Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 162d5b7a6d5fef6b24e1ad95497ba41db9e74c36c5083b68a0d042feb9631f40

Tx prefix hash: cf44ad65a7508bc45f4e41f1193df2bc479f4d9256886d3373bd251d56877d97
Tx public key: 67f96fbcf843be6ff0c368e03387c0fa41a1abe31f13c0426b5d59f3d2629a3b
Timestamp: 1755311040 Timestamp [UCT]: 2025-08-16 02:24:00 Age [y:d:h:m:s]: 00:111:20:04:30
Block: 1347583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79689 RingCT/type: yes/0
Extra: 0167f96fbcf843be6ff0c368e03387c0fa41a1abe31f13c0426b5d59f3d2629a3b021100000005ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73bc39dcce08c54d79e4934378a0e8ed769e6d6de9f0677c74f6caa1ae25ee4d 0.600000000000 1835502 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": 1347593, "vin": [ { "gen": { "height": 1347583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73bc39dcce08c54d79e4934378a0e8ed769e6d6de9f0677c74f6caa1ae25ee4d" } } ], "extra": [ 1, 103, 249, 111, 188, 248, 67, 190, 111, 240, 195, 104, 224, 51, 135, 192, 250, 65, 161, 171, 227, 31, 19, 192, 66, 107, 93, 89, 243, 210, 98, 154, 59, 2, 17, 0, 0, 0, 5, 173, 121, 72, 208, 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