Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d417d86342656b8a19d838dcb2837e0bb758abdd1df4ba5590b6ce9885986661

Tx prefix hash: baa22b25b54ccdf7d18d188cabf09c6ed0d1f697fa75b0c678fc0ed3bc5ab910
Tx public key: 4d32a7e8f61c8f06d12325a00cc9e0b633d850d248302a2a0184f83fa0aa64a9
Timestamp: 1735774061 Timestamp [UCT]: 2025-01-01 23:27:41 Age [y:d:h:m:s]: 00:165:04:48:47
Block: 1188192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117806 RingCT/type: yes/0
Extra: 014d32a7e8f61c8f06d12325a00cc9e0b633d850d248302a2a0184f83fa0aa64a9021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4b08d5eaab260ba87e8e06d45ca4740fc99099d290afcf167e617712ac6cce8 0.600000000000 1674693 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": 1188202, "vin": [ { "gen": { "height": 1188192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4b08d5eaab260ba87e8e06d45ca4740fc99099d290afcf167e617712ac6cce8" } } ], "extra": [ 1, 77, 50, 167, 232, 246, 28, 143, 6, 209, 35, 37, 160, 12, 201, 224, 182, 51, 216, 80, 210, 72, 48, 42, 42, 1, 132, 248, 63, 160, 170, 100, 169, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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