Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bf9291fd569f5c3bca162df6af8f46322996fed5804ae02c44921b4c5b00f38

Tx prefix hash: e76edf3cae9d241eefa921246c9a02ea5e29e9c05bc4bb2f4b1d406a81cfcebb
Tx public key: 6e3c5a2be8d89242da58300caa6510a47476056b75e3679c64f1645aa49ef2e8
Timestamp: 1759539788 Timestamp [UCT]: 2025-10-04 01:03:08 Age [y:d:h:m:s]: 00:054:06:54:05
Block: 1382244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38875 RingCT/type: yes/0
Extra: 016e3c5a2be8d89242da58300caa6510a47476056b75e3679c64f1645aa49ef2e802110000000597baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b777eecad12f89e31d88b534bf7d5aeabcdc0361868f7af6d14f4da52051b24 0.600000000000 1870379 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 dinasty-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": 1382254, "vin": [ { "gen": { "height": 1382244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b777eecad12f89e31d88b534bf7d5aeabcdc0361868f7af6d14f4da52051b24" } } ], "extra": [ 1, 110, 60, 90, 43, 232, 216, 146, 66, 218, 88, 48, 12, 170, 101, 16, 164, 116, 118, 5, 107, 117, 227, 103, 156, 100, 241, 100, 90, 164, 158, 242, 232, 2, 17, 0, 0, 0, 5, 151, 186, 249, 34, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8