Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 74d1e7ccf13d0b5bdd070c28ea607c389624facab8e51d4a20cdac44f2f1db8f

Tx prefix hash: bb22c0b0408bd0f6507c07a04056f8504a354308e2c74705e9ec194e894df68d
Tx public key: 54ce99c026aea4234397c3085999af432d7f75be38c05702815a31ace99030f7
Timestamp: 1742132420 Timestamp [UTC]: 2025-03-16 13:40:20 Age [y:d:h:m:s]: 01:241:09:15:20
Block: 1240595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436370 RingCT/type: yes/0
Extra: 0154ce99c026aea4234397c3085999af432d7f75be38c05702815a31ace99030f7021100000003007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 93e6b4a2797e8303931a8fde5d7cf0db826f17b3ec6a369c55f0155e31608adb 0.000600000000 1727568 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1240605, "vin": [ { "gen": { "height": 1240595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93e6b4a2797e8303931a8fde5d7cf0db826f17b3ec6a369c55f0155e31608adb" } } ], "extra": [ 1, 84, 206, 153, 192, 38, 174, 164, 35, 67, 151, 195, 8, 89, 153, 175, 67, 45, 127, 117, 190, 56, 192, 87, 2, 129, 90, 49, 172, 233, 144, 48, 247, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: