Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 333e445d62d3e733e06b80584b7da054bab5c0af50b83d87df40b612037d5975

Tx prefix hash: 445e4e5b3e28f815087c7af92d5944874b82e56e5e21e572dfd457e0030803ba
Tx public key: b156ad07579fe445afa5d18b5ad78be4ca976c5ceed194c8ca8019dc84b490b3
Timestamp: 1702147706 Timestamp [UCT]: 2023-12-09 18:48:26 Age [y:d:h:m:s]: 01:038:09:46:51
Block: 909554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288805 RingCT/type: yes/0
Extra: 01b156ad07579fe445afa5d18b5ad78be4ca976c5ceed194c8ca8019dc84b490b30211000000024b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b94581f226a175ea560d48d1a04385f2dd1063ea335001898c58513eaddf907d 0.600000000000 1366651 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": 909564, "vin": [ { "gen": { "height": 909554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b94581f226a175ea560d48d1a04385f2dd1063ea335001898c58513eaddf907d" } } ], "extra": [ 1, 177, 86, 173, 7, 87, 159, 228, 69, 175, 165, 209, 139, 90, 215, 139, 228, 202, 151, 108, 92, 238, 209, 148, 200, 202, 128, 25, 220, 132, 180, 144, 179, 2, 17, 0, 0, 0, 2, 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