Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3c20aa0d6a0580fbb3310928bc9766a983a6666392b65ad96a6bed1f054a208

Tx prefix hash: bce827107438caab55fb5379eea75707ca58d67f2c0bbd13470aa90eaaa2428c
Tx public key: 4d6bd7e5689d4a9fa41a72ccf6915236d3bbe3338d7fe4e3f3b121116d3f2409
Timestamp: 1754430220 Timestamp [UCT]: 2025-08-05 21:43:40 Age [y:d:h:m:s]: 00:060:01:18:59
Block: 1341040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41859 RingCT/type: yes/0
Extra: 014d6bd7e5689d4a9fa41a72ccf6915236d3bbe3338d7fe4e3f3b121116d3f2409021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b11f66826d0bdf06a0deed9a8dafe98d8ce80721313ea92c6b022d9df1868d5 0.600000000000 1828861 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": 1341050, "vin": [ { "gen": { "height": 1341040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b11f66826d0bdf06a0deed9a8dafe98d8ce80721313ea92c6b022d9df1868d5" } } ], "extra": [ 1, 77, 107, 215, 229, 104, 157, 74, 159, 164, 26, 114, 204, 246, 145, 82, 54, 211, 187, 227, 51, 141, 127, 228, 227, 243, 177, 33, 17, 109, 63, 36, 9, 2, 17, 0, 0, 0, 2, 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