Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aae0c99d64c9aa9abfa036c45580808df3ccc34fdce41ae01259184257be5e21

Tx prefix hash: 59c01973d597b1a01ef16f478f1ce2aa8cf1e6360d8867f6bcd4b077ded9eaa9
Tx public key: 7b30cc64994100bcaf4b7a25186863b974ce529ae7a3be76d26b812e26ba9ea7
Timestamp: 1773273533 Timestamp [UTC]: 2026-03-11 23:58:53 Age [y:d:h:m:s]: 00:249:11:42:39
Block: 1495844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183782 RingCT/type: yes/0
Extra: 017b30cc64994100bcaf4b7a25186863b974ce529ae7a3be76d26b812e26ba9ea7021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2a327e9843d4d2185f173cb60fd291f6322918a3672ae00cf8221773dc6a198b 0.000600000000 1985458 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": 1495854, "vin": [ { "gen": { "height": 1495844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a327e9843d4d2185f173cb60fd291f6322918a3672ae00cf8221773dc6a198b" } } ], "extra": [ 1, 123, 48, 204, 100, 153, 65, 0, 188, 175, 75, 122, 37, 24, 104, 99, 185, 116, 206, 82, 154, 231, 163, 190, 118, 210, 107, 129, 46, 38, 186, 158, 167, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: