Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d0e58df129efe2eaac001a4f005da3a4aeadad6437cff10689fe79ceaaaa58a

Tx prefix hash: 032afc61dc3c22019bd4e6434e03d2b79160a8987068b79df4ad820d796c26fa
Tx public key: 8c1d11bd45154612a01fd51a34f15f5ad6cae14a7c76f4c568ba87b61eeab4d1
Timestamp: 1713917796 Timestamp [UCT]: 2024-04-24 00:16:36 Age [y:d:h:m:s]: 01:009:02:11:57
Block: 1007130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267444 RingCT/type: yes/0
Extra: 018c1d11bd45154612a01fd51a34f15f5ad6cae14a7c76f4c568ba87b61eeab4d102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1cf124ba5f339cfbecd8aaff968e8a466b93e83b4aef1c62fb5667003ad8c10 0.600000000000 1468372 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": 1007140, "vin": [ { "gen": { "height": 1007130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1cf124ba5f339cfbecd8aaff968e8a466b93e83b4aef1c62fb5667003ad8c10" } } ], "extra": [ 1, 140, 29, 17, 189, 69, 21, 70, 18, 160, 31, 213, 26, 52, 241, 95, 90, 214, 202, 225, 74, 124, 118, 244, 197, 104, 186, 135, 182, 30, 234, 180, 209, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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