Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9b390c5d9d0807df7af9f5105031a97509dee5e9deffe14b658d0e41d72bc64

Tx prefix hash: ef3622cd533f9ba3bb1aba60def71df1267755b0546ea6b9db43c21f326ec154
Tx public key: e9c44c9a3ccf5531d716c3b59401d804415e073fa7416d0323bced031c6f4ce4
Timestamp: 1756437428 Timestamp [UCT]: 2025-08-29 03:17:08 Age [y:d:h:m:s]: 00:152:11:21:32
Block: 1356676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108858 RingCT/type: yes/0
Extra: 01e9c44c9a3ccf5531d716c3b59401d804415e073fa7416d0323bced031c6f4ce4021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c15c76519dc32b697dfac3c96ec0eb0761b60f73924c3d0eb8bcdea34cf3585 0.600000000000 1844685 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": 1356686, "vin": [ { "gen": { "height": 1356676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c15c76519dc32b697dfac3c96ec0eb0761b60f73924c3d0eb8bcdea34cf3585" } } ], "extra": [ 1, 233, 196, 76, 154, 60, 207, 85, 49, 215, 22, 195, 181, 148, 1, 216, 4, 65, 94, 7, 63, 167, 65, 109, 3, 35, 188, 237, 3, 28, 111, 76, 228, 2, 17, 0, 0, 0, 4, 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