Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45e9bcbdcac1b657b3d4205af95df8357cc72ac1448041f85ed3c3981eef0d15

Tx prefix hash: 29b20f8544572779dac88aee1e29daff981d80dd50882c1c8b6b54631d286a05
Tx public key: 0f0781fe7e2d76dc44e2d3fbdef9e4dd69100ab5bddbe42ce0489862bfb63bf5
Timestamp: 1765027278 Timestamp [UTC]: 2025-12-06 13:21:18 Age [y:d:h:m:s]: 00:349:20:41:05
Block: 1427721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255615 RingCT/type: yes/0
Extra: 010f0781fe7e2d76dc44e2d3fbdef9e4dd69100ab5bddbe42ce0489862bfb63bf502110000000170609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8add894feb3f5bf25387b4fda92a3a9665ef41d5b08e5edfc977b08991b37029 0.000600000000 1916424 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": 1427731, "vin": [ { "gen": { "height": 1427721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8add894feb3f5bf25387b4fda92a3a9665ef41d5b08e5edfc977b08991b37029" } } ], "extra": [ 1, 15, 7, 129, 254, 126, 45, 118, 220, 68, 226, 211, 251, 222, 249, 228, 221, 105, 16, 10, 181, 189, 219, 228, 44, 224, 72, 152, 98, 191, 182, 59, 245, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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: