Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddded4dc37f3671216a4ecb04ab910a9d7c450439744cc53b0257fe4822fb202

Tx prefix hash: 987cbfc6a14e32f4aa053e981ea3e3a78862ef24b103656258aca3d5c97731b9
Tx public key: 6383c12f95360fbc2c7139a066f9b3c2425784e88473d02bd86f96099d85d48f
Timestamp: 1774823169 Timestamp [UTC]: 2026-03-29 22:26:09 Age [y:d:h:m:s]: 00:050:07:13:53
Block: 1508657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29217 RingCT/type: yes/0
Extra: 016383c12f95360fbc2c7139a066f9b3c2425784e88473d02bd86f96099d85d48f021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7c03c31fa023132655a6f1b0a8193ddf501c4a833949f689709184f4771d9790 0.000600000000 1998411 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": 1508667, "vin": [ { "gen": { "height": 1508657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c03c31fa023132655a6f1b0a8193ddf501c4a833949f689709184f4771d9790" } } ], "extra": [ 1, 99, 131, 193, 47, 149, 54, 15, 188, 44, 113, 57, 160, 102, 249, 179, 194, 66, 87, 132, 232, 132, 115, 208, 43, 216, 111, 150, 9, 157, 133, 212, 143, 2, 17, 0, 0, 0, 4, 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: