Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9cb0527236c706a239d59efc19879d0032e587b83c4ca9d43f10cdb0809c6cd

Tx prefix hash: f7238ab3b583d21a18089e335cf90716c0b959417b7a194f8d206521029e726d
Tx public key: 360fa5f918de440b090f536803b46c68c1a5d800dc3a4e8acdafd77287ca6bfd
Timestamp: 1765122263 Timestamp [UCT]: 2025-12-07 15:44:23 Age [y:d:h:m:s]: 00:053:12:14:19
Block: 1428505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38135 RingCT/type: yes/0
Extra: 01360fa5f918de440b090f536803b46c68c1a5d800dc3a4e8acdafd77287ca6bfd02110000000570609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 308e2a5a5fe65971505b65e08790920eaf8126f553603acf35b00b27a89a8e2c 0.600000000000 1917222 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": 1428515, "vin": [ { "gen": { "height": 1428505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "308e2a5a5fe65971505b65e08790920eaf8126f553603acf35b00b27a89a8e2c" } } ], "extra": [ 1, 54, 15, 165, 249, 24, 222, 68, 11, 9, 15, 83, 104, 3, 180, 108, 104, 193, 165, 216, 0, 220, 58, 78, 138, 205, 175, 215, 114, 135, 202, 107, 253, 2, 17, 0, 0, 0, 5, 112, 96, 157, 3, 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