Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b91ab7c49d9ce5d99a79a1427c38ed38ad11e9b25ddfdef138774b3b2f3bf99c

Tx prefix hash: da9ff3755b082e4436b7ef2d11e1a2d5c9b2d998952a4c65804d67b82237f932
Tx public key: e0ad5b8dcdf5ffffea2a0ee8fc54ee8ef547e581637fe7fe05b3d17692a3c0d8
Timestamp: 1761980116 Timestamp [UCT]: 2025-11-01 06:55:16 Age [y:d:h:m:s]: 00:011:02:59:15
Block: 1402497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7936 RingCT/type: yes/0
Extra: 01e0ad5b8dcdf5ffffea2a0ee8fc54ee8ef547e581637fe7fe05b3d17692a3c0d802110000000bdf5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea1cf4f4e909f86efb8ba76a3ae0d843c85ddbb8c4619c18499702bdd7d3bb55 0.600000000000 1890816 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": 1402507, "vin": [ { "gen": { "height": 1402497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea1cf4f4e909f86efb8ba76a3ae0d843c85ddbb8c4619c18499702bdd7d3bb55" } } ], "extra": [ 1, 224, 173, 91, 141, 205, 245, 255, 255, 234, 42, 14, 232, 252, 84, 238, 142, 245, 71, 229, 129, 99, 127, 231, 254, 5, 179, 209, 118, 146, 163, 192, 216, 2, 17, 0, 0, 0, 11, 223, 90, 36, 122, 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