Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e436fccaf6ccf463d31dab3d24567d0645f2165fa4089b521e04a8d7300c94f

Tx prefix hash: d2744491bc42e625778a01fe7a8253bebb676712c35a2907419195f3a94614bf
Tx public key: 1cf6fd89462df62c30aa4685d64ba974826b8fd6c0356c83595f6fc813a894bb
Timestamp: 1760310254 Timestamp [UCT]: 2025-10-12 23:04:14 Age [y:d:h:m:s]: 00:040:00:08:01
Block: 1388627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28640 RingCT/type: yes/0
Extra: 011cf6fd89462df62c30aa4685d64ba974826b8fd6c0356c83595f6fc813a894bb0211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c58c91312dfd559a2a6f96ec429bfce9e82beb32974cb35c766615be5f8e2c06 0.600000000000 1876846 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": 1388637, "vin": [ { "gen": { "height": 1388627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c58c91312dfd559a2a6f96ec429bfce9e82beb32974cb35c766615be5f8e2c06" } } ], "extra": [ 1, 28, 246, 253, 137, 70, 45, 246, 44, 48, 170, 70, 133, 214, 75, 169, 116, 130, 107, 143, 214, 192, 53, 108, 131, 89, 95, 111, 200, 19, 168, 148, 187, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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