Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64d76fd967472d8054628370788bd17f590264cf8982030ad0b377782c18d7fd

Tx prefix hash: 25f03400db94a50f0146b9fec1e504718d9aa44d219468939c20d5029f37d5b2
Tx public key: 68d22d4d6b190f31802bb026d7ad74c71e01979ce8e2818d9e166b5a07c8addc
Timestamp: 1759852957 Timestamp [UCT]: 2025-10-07 16:02:37 Age [y:d:h:m:s]: 00:033:08:23:58
Block: 1384830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23890 RingCT/type: yes/0
Extra: 0168d22d4d6b190f31802bb026d7ad74c71e01979ce8e2818d9e166b5a07c8addc02110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63fd2ab514f593f233a58599f64d2f45db99a7b5b03f0146dee69b6128b3d4a9 0.600000000000 1872987 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": 1384840, "vin": [ { "gen": { "height": 1384830 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63fd2ab514f593f233a58599f64d2f45db99a7b5b03f0146dee69b6128b3d4a9" } } ], "extra": [ 1, 104, 210, 45, 77, 107, 25, 15, 49, 128, 43, 176, 38, 215, 173, 116, 199, 30, 1, 151, 156, 232, 226, 129, 141, 158, 22, 107, 90, 7, 200, 173, 220, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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