Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3fbb7361fc04fd30eb97f672cc17f762b7d514853bb5dcc20e75d9952fe7964

Tx prefix hash: 70f86c23e1d92838d4f1708bb8f39f8fdb0b4869d43e50be7f121e2de98490f7
Tx public key: 011294d4103c45e3947193d0dc8222dd0fdc44dcbae8b1b882869d005638d56c
Timestamp: 1754537924 Timestamp [UCT]: 2025-08-07 03:38:44 Age [y:d:h:m:s]: 00:059:21:27:23
Block: 1341891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41775 RingCT/type: yes/0
Extra: 01011294d4103c45e3947193d0dc8222dd0fdc44dcbae8b1b882869d005638d56c021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e50b9a6d076b7c4f8de88b9f19f49534b173cfc7b6e5abcaf3333f8424103a75 0.600000000000 1829720 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": 1341901, "vin": [ { "gen": { "height": 1341891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e50b9a6d076b7c4f8de88b9f19f49534b173cfc7b6e5abcaf3333f8424103a75" } } ], "extra": [ 1, 1, 18, 148, 212, 16, 60, 69, 227, 148, 113, 147, 208, 220, 130, 34, 221, 15, 220, 68, 220, 186, 232, 177, 184, 130, 134, 157, 0, 86, 56, 213, 108, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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