Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 965a015dd9d816b1249d1c56a3268dd29c60ed18c63426f56dea8fa0bdeddeba

Tx prefix hash: 2bd13e436d855f5677dae32205817babdd7b2183ed8e88d4c6e6281a1d874b6a
Tx public key: d51542b77b0faf8b3d6cfd282fda67ac94be829ca7058e833546237fd9a4fb36
Timestamp: 1719332674 Timestamp [UCT]: 2024-06-25 16:24:34 Age [y:d:h:m:s]: 00:278:14:35:20
Block: 1052012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199080 RingCT/type: yes/0
Extra: 01d51542b77b0faf8b3d6cfd282fda67ac94be829ca7058e833546237fd9a4fb360211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7d41de8e397d05c70a7132443ee66a9d68cefca366bdf2e4ef0fc2fca6fc966 0.600000000000 1522333 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": 1052022, "vin": [ { "gen": { "height": 1052012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7d41de8e397d05c70a7132443ee66a9d68cefca366bdf2e4ef0fc2fca6fc966" } } ], "extra": [ 1, 213, 21, 66, 183, 123, 15, 175, 139, 61, 108, 253, 40, 47, 218, 103, 172, 148, 190, 130, 156, 167, 5, 142, 131, 53, 70, 35, 127, 217, 164, 251, 54, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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