Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e99cd4de8a9d27aaef7a16f587c0f6137db5cdcaf939ace69c48380e3a4f2ee

Tx prefix hash: 0aa03eb4138460dc95ef36023a69715bb520e4914b1f81794aed087d80e22f2d
Tx public key: 1704ca6c6f4b8c73964ecb06f4e3e9e846821774775dcc3429721a8a5421f54f
Timestamp: 1774740408 Timestamp [UTC]: 2026-03-28 23:26:48 Age [y:d:h:m:s]: 00:233:05:11:29
Block: 1507971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172175 RingCT/type: yes/0
Extra: 011704ca6c6f4b8c73964ecb06f4e3e9e846821774775dcc3429721a8a5421f54f021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9cd197d5cb1804265fc8b7a3e29b151a3703c074c3a93897c11ef06c69c1836d 0.000600000000 1997723 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": 1507981, "vin": [ { "gen": { "height": 1507971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cd197d5cb1804265fc8b7a3e29b151a3703c074c3a93897c11ef06c69c1836d" } } ], "extra": [ 1, 23, 4, 202, 108, 111, 75, 140, 115, 150, 78, 203, 6, 244, 227, 233, 232, 70, 130, 23, 116, 119, 93, 204, 52, 41, 114, 26, 138, 84, 33, 245, 79, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: