Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 871cdc1bd166d7ab22c89b68f4a73a7d026614fff99c6dd3da136ac042a92f4c

Tx prefix hash: 02c3fb8270ad3c17d63ab77d01a8802361a91254c06046785e682e97d3c705af
Tx public key: 0ee69f839292196ffcc44650d0e581ae1a34f46196320ae0981cec9b5d985066
Timestamp: 1703728787 Timestamp [UCT]: 2023-12-28 01:59:47 Age [y:d:h:m:s]: 01:341:17:26:25
Block: 922658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503113 RingCT/type: yes/0
Extra: 010ee69f839292196ffcc44650d0e581ae1a34f46196320ae0981cec9b5d985066021100000008ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96b94c2ad2f3a4a1188bdf0a64df9d80f1aaea2e185f58e3dd30649b5965b654 0.600000000000 1380362 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": 922668, "vin": [ { "gen": { "height": 922658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96b94c2ad2f3a4a1188bdf0a64df9d80f1aaea2e185f58e3dd30649b5965b654" } } ], "extra": [ 1, 14, 230, 159, 131, 146, 146, 25, 111, 252, 196, 70, 80, 208, 229, 129, 174, 26, 52, 244, 97, 150, 50, 10, 224, 152, 28, 236, 155, 93, 152, 80, 102, 2, 17, 0, 0, 0, 8, 173, 86, 148, 172, 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