Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 439296a5e42a2efaecced850536dd53257442983fb79bab93d481c3421bcf0b3

Tx prefix hash: b5fcfb1dab259123c29227c4377d86123ee95e8cf497e3e5f54a54ae9338a49a
Tx public key: db2b88bc2f883bc46d4302cdc0960cd5c903b73991c53b294051c2880d85b917
Timestamp: 1656967374 Timestamp [UCT]: 2022-07-04 20:42:54 Age [y:d:h:m:s]: 02:223:10:54:19
Block: 536683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 680822 RingCT/type: yes/0
Extra: 01db2b88bc2f883bc46d4302cdc0960cd5c903b73991c53b294051c2880d85b91702110000000b75e3f0e9000000000000000000

1 output(s) for total of 10.226960653000 dcy

stealth address amount amount idx
00: 1cc463810ea002cbaf6ea2ca6a7df2cdd8e91bca05b91bb351ab62bb83da8c0f 10.226960653000 966472 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": 536693, "vin": [ { "gen": { "height": 536683 } } ], "vout": [ { "amount": 10226960653, "target": { "key": "1cc463810ea002cbaf6ea2ca6a7df2cdd8e91bca05b91bb351ab62bb83da8c0f" } } ], "extra": [ 1, 219, 43, 136, 188, 47, 136, 59, 196, 109, 67, 2, 205, 192, 150, 12, 213, 201, 3, 183, 57, 145, 197, 59, 41, 64, 81, 194, 136, 13, 133, 185, 23, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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