Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9668c137a12c660ccd9cb16b9dc2d27bac932fe31bb8c9ed1c4f3d9079b8bc0c

Tx prefix hash: 37acfcd5ea4cabc27c1e3c8dbda1941097a9639171c5d3102c10f5ce060e7c15
Tx public key: 625330aa0d4677e2013b67878e0e15511c26fe1019067b4016972d265dc3d2b0
Timestamp: 1770453032 Timestamp [UTC]: 2026-02-07 08:30:32 Age [y:d:h:m:s]: 00:008:17:14:54
Block: 1472524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 6205 RingCT/type: yes/0
Extra: 01625330aa0d4677e2013b67878e0e15511c26fe1019067b4016972d265dc3d2b00208cfe3dea90e6ae588

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ab14e909ddcaf0741b03d35e7e0c76a9fe30c3a7c8dccce733fffb5f2a82ab6b 0.000600000000 1961804 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": 1472534, "vin": [ { "gen": { "height": 1472524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab14e909ddcaf0741b03d35e7e0c76a9fe30c3a7c8dccce733fffb5f2a82ab6b" } } ], "extra": [ 1, 98, 83, 48, 170, 13, 70, 119, 226, 1, 59, 103, 135, 142, 14, 21, 81, 28, 38, 254, 16, 25, 6, 123, 64, 22, 151, 45, 38, 93, 195, 210, 176, 2, 8, 207, 227, 222, 169, 14, 106, 229, 136 ], "rct_signatures": { "type": 0 } }


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