Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a40a96d7b74b25b9a9239332f908b4cea5996cabcb1ece83d995d552ad77ac68

Tx prefix hash: f8648faf578520f0aef9bce416d40fb771f7794ad290a2f9d2803f3af5de3d38
Tx public key: d08ed87b6ca4bb9a2f6c77a72b5c4b1c43e26f90dd63b402b788a053fac6f3ee
Timestamp: 1703817215 Timestamp [UCT]: 2023-12-29 02:33:35 Age [y:d:h:m:s]: 01:018:00:25:17
Block: 923385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274217 RingCT/type: yes/0
Extra: 01d08ed87b6ca4bb9a2f6c77a72b5c4b1c43e26f90dd63b402b788a053fac6f3ee0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc0942cd74010645eda93505eb5e29c7db33171e59e3f3a19bf9775174ec226b 0.600000000000 1381117 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": 923395, "vin": [ { "gen": { "height": 923385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc0942cd74010645eda93505eb5e29c7db33171e59e3f3a19bf9775174ec226b" } } ], "extra": [ 1, 208, 142, 216, 123, 108, 164, 187, 154, 47, 108, 119, 167, 43, 92, 75, 28, 67, 226, 111, 144, 221, 99, 180, 2, 183, 136, 160, 83, 250, 198, 243, 238, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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