Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f0e04b392f701114edc4353f56c2d8666cbc674d59393e1173bcb49e66e2be9

Tx prefix hash: 068575768f290597a2a73d87820008b4c9320ef8eb1c1f7c3c8b840b6c9ebcdb
Tx public key: 7425fb475e062e53859b63ac080413c4e05e897d2ce08538b94e7be4a2e1188c
Timestamp: 1713325942 Timestamp [UCT]: 2024-04-17 03:52:22 Age [y:d:h:m:s]: 01:030:10:03:02
Block: 1002213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282718 RingCT/type: yes/0
Extra: 017425fb475e062e53859b63ac080413c4e05e897d2ce08538b94e7be4a2e1188c02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ee94348c22108e9d1fa6605e14a55468d3df2723cc98a7338683920555d0045 0.600000000000 1462729 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": 1002223, "vin": [ { "gen": { "height": 1002213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ee94348c22108e9d1fa6605e14a55468d3df2723cc98a7338683920555d0045" } } ], "extra": [ 1, 116, 37, 251, 71, 94, 6, 46, 83, 133, 155, 99, 172, 8, 4, 19, 196, 224, 94, 137, 125, 44, 224, 133, 56, 185, 78, 123, 228, 162, 225, 24, 140, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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