Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87271e4269a0752b1f32ae8dd3f3d93e48f79ea9d97e30af76ecc32f1b5d7ff7

Tx prefix hash: 732ee4311f752203a787d235f602df83973f54a25f907b28b407b8d675731e5f
Tx public key: aded8a37cd8432a9c2cd77ab183d3d45571167d6a7cf0a48ac2d72a3f8527c85
Timestamp: 1760399593 Timestamp [UCT]: 2025-10-13 23:53:13 Age [y:d:h:m:s]: 00:081:19:47:01
Block: 1389382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58587 RingCT/type: yes/0
Extra: 01aded8a37cd8432a9c2cd77ab183d3d45571167d6a7cf0a48ac2d72a3f8527c850211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0adea38a78c82778de05441da36b4b9e577527205cd00f61ae628c243148584c 0.600000000000 1877611 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": 1389392, "vin": [ { "gen": { "height": 1389382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0adea38a78c82778de05441da36b4b9e577527205cd00f61ae628c243148584c" } } ], "extra": [ 1, 173, 237, 138, 55, 205, 132, 50, 169, 194, 205, 119, 171, 24, 61, 61, 69, 87, 17, 103, 214, 167, 207, 10, 72, 172, 45, 114, 163, 248, 82, 124, 133, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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