Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f29145f11480a867c2a3810054bcb2da7fe45c70626352ef1e30c14f9b066436

Tx prefix hash: debd7fe4c53eed422d7e6c1434a2abaace70c19f7639e27c6ab8a95aab23a576
Tx public key: 20c16c91d1d2006f2b2a2e84f9d2df9fae19ebe8bb03114bd2ee0b47ed7d85e1
Timestamp: 1701482780 Timestamp [UCT]: 2023-12-02 02:06:20 Age [y:d:h:m:s]: 01:084:12:29:19
Block: 904023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321533 RingCT/type: yes/0
Extra: 0120c16c91d1d2006f2b2a2e84f9d2df9fae19ebe8bb03114bd2ee0b47ed7d85e102110000000233af99f4000000000000000000

1 output(s) for total of 0.620292458000 dcy

stealth address amount amount idx
00: 500fe7ff0be5bfdb5e99cd5a76204516de7355e9ce9483d9246af55861fc2ad6 0.620292458000 1360726 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": 904033, "vin": [ { "gen": { "height": 904023 } } ], "vout": [ { "amount": 620292458, "target": { "key": "500fe7ff0be5bfdb5e99cd5a76204516de7355e9ce9483d9246af55861fc2ad6" } } ], "extra": [ 1, 32, 193, 108, 145, 209, 210, 0, 111, 43, 42, 46, 132, 249, 210, 223, 159, 174, 25, 235, 232, 187, 3, 17, 75, 210, 238, 11, 71, 237, 125, 133, 225, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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