Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99c2dfd923328cf2c3d8974706c78b5014ea7e1701775a5b25cda9d647ea46e1

Tx prefix hash: 28228770ba8952325947ba4a7069ddde1581c5fcb62d54f7ee3dd7c6e9a2d06e
Tx public key: 072caacbfa9d6818f0c16f8b471bfb2b921690f0aff3e15783ef50461416081d
Timestamp: 1708487039 Timestamp [UCT]: 2024-02-21 03:43:59 Age [y:d:h:m:s]: 01:260:01:11:28
Block: 962103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444599 RingCT/type: yes/0
Extra: 01072caacbfa9d6818f0c16f8b471bfb2b921690f0aff3e15783ef50461416081d02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c677db398dc00c90d6a717c2ee0fa5192a54dff5e70a21b8356de61aa9d9878 0.600000000000 1421726 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": 962113, "vin": [ { "gen": { "height": 962103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c677db398dc00c90d6a717c2ee0fa5192a54dff5e70a21b8356de61aa9d9878" } } ], "extra": [ 1, 7, 44, 170, 203, 250, 157, 104, 24, 240, 193, 111, 139, 71, 27, 251, 43, 146, 22, 144, 240, 175, 243, 225, 87, 131, 239, 80, 70, 20, 22, 8, 29, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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