Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2caedebd6a793c63bddd3665022f850d43d022e4bb6800c9b1578b70d4450bcd

Tx prefix hash: 6b6a57e99ddc5442963873f462fd3380912ea7d22ccffe86ce0427ca75a343c3
Tx public key: dc1afc470116f16fe8fa19134d210778a54b9dd1ca1bfd0c2d038dbf7ca6a17f
Timestamp: 1747253926 Timestamp [UCT]: 2025-05-14 20:18:46 Age [y:d:h:m:s]: 00:146:11:16:36
Block: 1282977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102324 RingCT/type: yes/0
Extra: 01dc1afc470116f16fe8fa19134d210778a54b9dd1ca1bfd0c2d038dbf7ca6a17f02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5682275eae9cc290dd669e616b49d1d89f8e87117b8daa11128b0befa6570eba 0.600000000000 1770392 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": 1282987, "vin": [ { "gen": { "height": 1282977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5682275eae9cc290dd669e616b49d1d89f8e87117b8daa11128b0befa6570eba" } } ], "extra": [ 1, 220, 26, 252, 71, 1, 22, 241, 111, 232, 250, 25, 19, 77, 33, 7, 120, 165, 75, 157, 209, 202, 27, 253, 12, 45, 3, 141, 191, 124, 166, 161, 127, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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