Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06034c374570bbd42157a88bdf48df6e581be4bd805cced72db35649479bdb19

Tx prefix hash: 5aab5a9660fefdd4eb7c19074d730e72a77ad95f62ea0fbfb008fb22475a619a
Tx public key: 805cebe208ea1351b03da822fd261a4dc5a5dfdfab145cb278c0741fde0d6590
Timestamp: 1751570565 Timestamp [UCT]: 2025-07-03 19:22:45 Age [y:d:h:m:s]: 00:131:13:49:29
Block: 1318122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92288 RingCT/type: yes/0
Extra: 01805cebe208ea1351b03da822fd261a4dc5a5dfdfab145cb278c0741fde0d6590021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0eddb4cc0338fc4c0953ecd5f0ec2eebc982e76c945321f7ef429e3bb93f243 0.600000000000 1805795 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": 1318132, "vin": [ { "gen": { "height": 1318122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0eddb4cc0338fc4c0953ecd5f0ec2eebc982e76c945321f7ef429e3bb93f243" } } ], "extra": [ 1, 128, 92, 235, 226, 8, 234, 19, 81, 176, 61, 168, 34, 253, 38, 26, 77, 197, 165, 223, 223, 171, 20, 92, 178, 120, 192, 116, 31, 222, 13, 101, 144, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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