Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc4df3bfb7e0ee0e20983381d7a297ef3e038292e4a395b353f1bbdc010d7a52

Tx prefix hash: 655bb32e0b1385923f0f5bdd935ab6e998dfa80b8c621bc39ca9388a9db2d339
Tx public key: e3c6c8680f92a07b3f90a20b94b87cb5e65d5470bcf938ee772fdeae5dde484b
Timestamp: 1699495023 Timestamp [UCT]: 2023-11-09 01:57:03 Age [y:d:h:m:s]: 01:146:11:11:58
Block: 887566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365858 RingCT/type: yes/0
Extra: 01e3c6c8680f92a07b3f90a20b94b87cb5e65d5470bcf938ee772fdeae5dde484b0211000000014b8f5122000000000000000000

1 output(s) for total of 0.703275353000 dcy

stealth address amount amount idx
00: ac917e0f4a8453ba4fe82f0c749cf01e222890618515a37ae79e6bd30374a1f3 0.703275353000 1343453 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": 887576, "vin": [ { "gen": { "height": 887566 } } ], "vout": [ { "amount": 703275353, "target": { "key": "ac917e0f4a8453ba4fe82f0c749cf01e222890618515a37ae79e6bd30374a1f3" } } ], "extra": [ 1, 227, 198, 200, 104, 15, 146, 160, 123, 63, 144, 162, 11, 148, 184, 124, 181, 230, 93, 84, 112, 188, 249, 56, 238, 119, 47, 222, 174, 93, 222, 72, 75, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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