Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57da28a610c6d66f2d4d8205fd0ce95607f68144983f46b2e4b8b3cf04f6a29a

Tx prefix hash: 6fb77ee5b15756a3237866f89873a0d57064466672e500c8050b5a1de955509d
Tx public key: ed181376e05e13b211e0a4d9ceb7e215e9284e97ef36518e5e2c4d9ed9414187
Timestamp: 1581703065 Timestamp [UCT]: 2020-02-14 17:57:45 Age [y:d:h:m:s]: 04:360:12:51:20
Block: 65207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149412 RingCT/type: yes/0
Extra: 01ed181376e05e13b211e0a4d9ceb7e215e9284e97ef36518e5e2c4d9ed941418702110000000456c366d3000000000000000000

1 output(s) for total of 373.201130799000 dcy

stealth address amount amount idx
00: d7b671ecfd1f4f4b0ae21074a80d7a8ac2dde8b40bab6a32b23ecabf8192f058 373.201130799000 120210 of 0

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": 65217, "vin": [ { "gen": { "height": 65207 } } ], "vout": [ { "amount": 373201130799, "target": { "key": "d7b671ecfd1f4f4b0ae21074a80d7a8ac2dde8b40bab6a32b23ecabf8192f058" } } ], "extra": [ 1, 237, 24, 19, 118, 224, 94, 19, 178, 17, 224, 164, 217, 206, 183, 226, 21, 233, 40, 78, 151, 239, 54, 81, 142, 94, 44, 77, 158, 217, 65, 65, 135, 2, 17, 0, 0, 0, 4, 86, 195, 102, 211, 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