Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7d3cca74fbb80ba74a8f72495cadfc2df4d01501ef674f3eb0cef9640f1654b

Tx prefix hash: 239a01686de09ec5e534ef663ab02f828c3801efdcbefbecefb6fe684e09b985
Tx public key: a6955ef61455dc76bfd914c02a5a228e6056bb8ebd6716c26481d35b667502b1
Timestamp: 1728625065 Timestamp [UCT]: 2024-10-11 05:37:45 Age [y:d:h:m:s]: 00:180:02:30:46
Block: 1129058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128514 RingCT/type: yes/0
Extra: 01a6955ef61455dc76bfd914c02a5a228e6056bb8ebd6716c26481d35b667502b1021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d0a71fe07833941aa71387c5e881b18737ed3285050b4d945e6d3048e9d3d5e 0.600000000000 1611881 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": 1129068, "vin": [ { "gen": { "height": 1129058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d0a71fe07833941aa71387c5e881b18737ed3285050b4d945e6d3048e9d3d5e" } } ], "extra": [ 1, 166, 149, 94, 246, 20, 85, 220, 118, 191, 217, 20, 192, 42, 90, 34, 142, 96, 86, 187, 142, 189, 103, 22, 194, 100, 129, 211, 91, 102, 117, 2, 177, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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