Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c0517f61a9ec733f846be64c19b233d9e06cc3e51213de30b843223031d0087

Tx prefix hash: 618abe5aba002c50820e0e598f15e20f094b8a428b86e9f982867fcff8c68252
Tx public key: cc882fb3be3fcbcb0736916874c78b6288757d107c8de636ecc69a12c8aa7e87
Timestamp: 1757611448 Timestamp [UCT]: 2025-09-11 17:24:08 Age [y:d:h:m:s]: 00:119:00:25:48
Block: 1366255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85239 RingCT/type: yes/0
Extra: 01cc882fb3be3fcbcb0736916874c78b6288757d107c8de636ecc69a12c8aa7e87021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00d0abf1ea021c22b3fcc977aa77f1c8dacb253e35379b20b26e7d98a1b5ae24 0.600000000000 1854294 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": 1366265, "vin": [ { "gen": { "height": 1366255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00d0abf1ea021c22b3fcc977aa77f1c8dacb253e35379b20b26e7d98a1b5ae24" } } ], "extra": [ 1, 204, 136, 47, 179, 190, 63, 203, 203, 7, 54, 145, 104, 116, 199, 139, 98, 136, 117, 125, 16, 124, 141, 230, 54, 236, 198, 154, 18, 200, 170, 126, 135, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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