Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60196f8237127af172c1881750c4d56e8c6e2ec0cf8552b87a62acd47e5c1e5f

Tx prefix hash: e13b5f6b71decf3ed1572f30bb3d26b8899b6980fdd39a56bbbad0a615aaf235
Tx public key: 8aa53e382bf05c1609c8d8e657ceefc829bc6462228673f8bc0e4a9352e829e8
Timestamp: 1720913679 Timestamp [UCT]: 2024-07-13 23:34:39 Age [y:d:h:m:s]: 00:290:23:15:37
Block: 1065141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207887 RingCT/type: yes/0
Extra: 018aa53e382bf05c1609c8d8e657ceefc829bc6462228673f8bc0e4a9352e829e802110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03cdad026aca91172f6b8e3c57db7e44dbd41dd2014f7b9ac556121e37ea1afb 0.600000000000 1535684 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": 1065151, "vin": [ { "gen": { "height": 1065141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03cdad026aca91172f6b8e3c57db7e44dbd41dd2014f7b9ac556121e37ea1afb" } } ], "extra": [ 1, 138, 165, 62, 56, 43, 240, 92, 22, 9, 200, 216, 230, 87, 206, 239, 200, 41, 188, 100, 98, 34, 134, 115, 248, 188, 14, 74, 147, 82, 232, 41, 232, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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