Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d02ceeed148b202df8a721193147b5a1ae1bac863de9b9d7b29fe6ff9a95171

Tx prefix hash: 519521a09c650f287867f8110c948f438fa84a4eea9c08fd5f75e5f674a9c740
Tx public key: 785d5915eaabb0845cd5737a0bf8c0499b8410cfac8332a3ab2d4b3e122b68d7
Timestamp: 1754616179 Timestamp [UCT]: 2025-08-08 01:22:59 Age [y:d:h:m:s]: 00:073:18:20:46
Block: 1342487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51795 RingCT/type: yes/0
Extra: 01785d5915eaabb0845cd5737a0bf8c0499b8410cfac8332a3ab2d4b3e122b68d7021100000007b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c263b4c50289bc3a34efd46c5ed1dd605cb977f6b16f918064d5bee5106751d0 0.600000000000 1830318 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": 1342497, "vin": [ { "gen": { "height": 1342487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c263b4c50289bc3a34efd46c5ed1dd605cb977f6b16f918064d5bee5106751d0" } } ], "extra": [ 1, 120, 93, 89, 21, 234, 171, 176, 132, 92, 213, 115, 122, 11, 248, 192, 73, 155, 132, 16, 207, 172, 131, 50, 163, 171, 45, 75, 62, 18, 43, 104, 215, 2, 17, 0, 0, 0, 7, 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