Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 128618b0a4f086da8ddcb84fc39e0c7456fc622a441a23175d9b0f8dfd532ba2

Tx prefix hash: 00b27671db4eb2a5e9aeb1bd7c3711ae526804c2b7bba2ba9a308388d958ca3f
Tx public key: 8934ce61d5156c03dd6779736b60b4eb7a20a1938e264339f2d9c26c73a3e344
Timestamp: 1762142168 Timestamp [UCT]: 2025-11-03 03:56:08 Age [y:d:h:m:s]: 00:061:03:55:45
Block: 1403805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43809 RingCT/type: yes/0
Extra: 018934ce61d5156c03dd6779736b60b4eb7a20a1938e264339f2d9c26c73a3e3440211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d19f6242007422945e9647be4d5f4a2b6f7de91fe8a4cfa1ff149f64a2ef964 0.600000000000 1892158 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": 1403815, "vin": [ { "gen": { "height": 1403805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d19f6242007422945e9647be4d5f4a2b6f7de91fe8a4cfa1ff149f64a2ef964" } } ], "extra": [ 1, 137, 52, 206, 97, 213, 21, 108, 3, 221, 103, 121, 115, 107, 96, 180, 235, 122, 32, 161, 147, 142, 38, 67, 57, 242, 217, 194, 108, 115, 163, 227, 68, 2, 17, 0, 0, 0, 1, 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