Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e8e5a960ccd599558758f77ca4c5aa899ec7c47b0738ec1a00fdb50312b5927

Tx prefix hash: 721518c193dedfce5001f341d6899ebe326ac670cf0248c648017846877dd87a
Tx public key: 4ec3398e4b7aebe9f28f973aabf33a864a924c13738c3defa8e570f738af9a0c
Timestamp: 1713680868 Timestamp [UCT]: 2024-04-21 06:27:48 Age [y:d:h:m:s]: 00:350:12:06:15
Block: 1005160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250561 RingCT/type: yes/0
Extra: 014ec3398e4b7aebe9f28f973aabf33a864a924c13738c3defa8e570f738af9a0c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5777d891700b9b6f327acc5ebbc9c30c5814e35917e6d41e5189f5a6b8c05b82 0.600000000000 1465740 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": 1005170, "vin": [ { "gen": { "height": 1005160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5777d891700b9b6f327acc5ebbc9c30c5814e35917e6d41e5189f5a6b8c05b82" } } ], "extra": [ 1, 78, 195, 57, 142, 75, 122, 235, 233, 242, 143, 151, 58, 171, 243, 58, 134, 74, 146, 76, 19, 115, 140, 61, 239, 168, 229, 112, 247, 56, 175, 154, 12, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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