Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef9296d7cc6e4b1029c8a8d54a94cf4add752d7cf26a2229bfdd724990735b3c

Tx prefix hash: 65886e7f7faddeb4a7009f055fc44206180a6d38d811ea3480ca7309d15b3cd4
Tx public key: df9bd94fd1911e10e43835d88bd8ab725c244c947895df680caeec7fa8dc0fc8
Timestamp: 1711926496 Timestamp [UCT]: 2024-03-31 23:08:16 Age [y:d:h:m:s]: 01:079:14:00:03
Block: 990639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317741 RingCT/type: yes/0
Extra: 01df9bd94fd1911e10e43835d88bd8ab725c244c947895df680caeec7fa8dc0fc802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af9f635d4e89fb409a0c8493a78d6cdc644603576fefb0d7e7e11e67354c1a3f 0.600000000000 1450963 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": 990649, "vin": [ { "gen": { "height": 990639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af9f635d4e89fb409a0c8493a78d6cdc644603576fefb0d7e7e11e67354c1a3f" } } ], "extra": [ 1, 223, 155, 217, 79, 209, 145, 30, 16, 228, 56, 53, 216, 139, 216, 171, 114, 92, 36, 76, 148, 120, 149, 223, 104, 12, 174, 236, 127, 168, 220, 15, 200, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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