Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d91c63cdf25bb55947503121fd3689ae32f55a72627516a3c946105d680cfc6f

Tx prefix hash: c68864a92e92caaac34b0ff38debde37fdbe3a211e55056e913c6ac49e783dd9
Tx public key: 47d92214a4c4c4223c67e4b680bd36797fc61b99f56f61f429dd0318ad053d9a
Timestamp: 1758187930 Timestamp [UCT]: 2025-09-18 09:32:10 Age [y:d:h:m:s]: 00:062:22:29:19
Block: 1371049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45056 RingCT/type: yes/0
Extra: 0147d92214a4c4c4223c67e4b680bd36797fc61b99f56f61f429dd0318ad053d9a021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c189a5af1b667bc70ae7cbd58326ea3e3c1ac7827d1958e8b39e8d9c5a1c6b59 0.600000000000 1859126 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": 1371059, "vin": [ { "gen": { "height": 1371049 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c189a5af1b667bc70ae7cbd58326ea3e3c1ac7827d1958e8b39e8d9c5a1c6b59" } } ], "extra": [ 1, 71, 217, 34, 20, 164, 196, 196, 34, 60, 103, 228, 182, 128, 189, 54, 121, 127, 198, 27, 153, 245, 111, 97, 244, 41, 221, 3, 24, 173, 5, 61, 154, 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