Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd7187c2b8d8c1ef95205dd8208b095b0a33a11fb52beb770421c98056bcad19

Tx prefix hash: 283d23131af520d0aa7c5008940c49fe853ad9361e7113e6a7eb599473cc6d25
Tx public key: ca33139071a3b9086ed25d50f0a7bdffcff5a2b4b44b3d26609d9b70188717c4
Timestamp: 1754648561 Timestamp [UCT]: 2025-08-08 10:22:41 Age [y:d:h:m:s]: 00:050:08:32:54
Block: 1342749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35011 RingCT/type: yes/0
Extra: 01ca33139071a3b9086ed25d50f0a7bdffcff5a2b4b44b3d26609d9b70188717c4021100000006b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18a5620d5765c6bae6476fdd0fd3ead7dece8e9522ba81711267c9ede209ea12 0.600000000000 1830582 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": 1342759, "vin": [ { "gen": { "height": 1342749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18a5620d5765c6bae6476fdd0fd3ead7dece8e9522ba81711267c9ede209ea12" } } ], "extra": [ 1, 202, 51, 19, 144, 113, 163, 185, 8, 110, 210, 93, 80, 240, 167, 189, 255, 207, 245, 162, 180, 180, 75, 61, 38, 96, 157, 155, 112, 24, 135, 23, 196, 2, 17, 0, 0, 0, 6, 178, 247, 132, 196, 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