Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 202c81b68b51464e827628b068f0960b8d9479872d58ee8d032798a266b14300

Tx prefix hash: c3dbdd59b2e6f35a6e575b911f765447ebad9d179a462ec5a8b738e85e09c758
Tx public key: 15f6ea10cfd8bf58801b6c3bd34f671b264a2d69e536fbec47d9dda12aeb8152
Timestamp: 1703349224 Timestamp [UCT]: 2023-12-23 16:33:44 Age [y:d:h:m:s]: 01:132:10:07:57
Block: 919510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355777 RingCT/type: yes/0
Extra: 0115f6ea10cfd8bf58801b6c3bd34f671b264a2d69e536fbec47d9dda12aeb815202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53239b6c735b07aee681ef90e708b6f37f3a3e0f7c2fb24e5043309aa0a85723 0.600000000000 1377184 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": 919520, "vin": [ { "gen": { "height": 919510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53239b6c735b07aee681ef90e708b6f37f3a3e0f7c2fb24e5043309aa0a85723" } } ], "extra": [ 1, 21, 246, 234, 16, 207, 216, 191, 88, 128, 27, 108, 59, 211, 79, 103, 27, 38, 74, 45, 105, 229, 54, 251, 236, 71, 217, 221, 161, 42, 235, 129, 82, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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