Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11d00c7f7657688a2e2e425fe1c586b459937c31a9e5443bbce46857d0661ee5

Tx prefix hash: 355ebfc77ab9a2477e83908b02a063096408e90502b3d2456f4f3b9ea6fa3271
Tx public key: c244b0b9f1d9f7657a503f8d86944df7f808a044113c80854ccdda536518a2fb
Timestamp: 1749101289 Timestamp [UCT]: 2025-06-05 05:28:09 Age [y:d:h:m:s]: 00:169:17:02:52
Block: 1298270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118982 RingCT/type: yes/0
Extra: 01c244b0b9f1d9f7657a503f8d86944df7f808a044113c80854ccdda536518a2fb02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c8cb36028c1c2115c0d453b3f0041af62d24b1e6169034a23742ad96731651f 0.600000000000 1785793 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": 1298280, "vin": [ { "gen": { "height": 1298270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c8cb36028c1c2115c0d453b3f0041af62d24b1e6169034a23742ad96731651f" } } ], "extra": [ 1, 194, 68, 176, 185, 241, 217, 247, 101, 122, 80, 63, 141, 134, 148, 77, 247, 248, 8, 160, 68, 17, 60, 128, 133, 76, 205, 218, 83, 101, 24, 162, 251, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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