Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9ad113ab7e36c1ee932c4e56f9f0e29b9f2f345a03a651fc2bd64fa7cb39eee

Tx prefix hash: b32d12ff0f72a01a60680abddc2ab2ae7ade011cee5d24288c1bcf1fdc693264
Tx public key: c6bf3e0aa4fd37a2bab7ff37cde2e9ee8b5dcff0ecdb115f6e37ddd3672b078d
Timestamp: 1737545431 Timestamp [UCT]: 2025-01-22 11:30:31 Age [y:d:h:m:s]: 00:051:04:34:52
Block: 1202818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36415 RingCT/type: yes/0
Extra: 01c6bf3e0aa4fd37a2bab7ff37cde2e9ee8b5dcff0ecdb115f6e37ddd3672b078d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db17d498d3e43c327c9b66ebc56e0d622900438e088f7472ff92775f18db21c8 0.600000000000 1689485 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": 1202828, "vin": [ { "gen": { "height": 1202818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db17d498d3e43c327c9b66ebc56e0d622900438e088f7472ff92775f18db21c8" } } ], "extra": [ 1, 198, 191, 62, 10, 164, 253, 55, 162, 186, 183, 255, 55, 205, 226, 233, 238, 139, 93, 207, 240, 236, 219, 17, 95, 110, 55, 221, 211, 103, 43, 7, 141, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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