Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e61fc28edc60f78e49364717b79d9ce3e590f0e69b3d7dc99fb02b0d3d1ef4e

Tx prefix hash: f88c7171ed4c6b4b1422e0a48b7291f39473ab71047e327c6fcb8b0912b05ee1
Tx public key: 3c08065f2860bdfcb482fa13347b5ea324b73bde4c054fc6f397e572ce91d2f2
Timestamp: 1712065370 Timestamp [UCT]: 2024-04-02 13:42:50 Age [y:d:h:m:s]: 01:021:08:34:22
Block: 991745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276251 RingCT/type: yes/0
Extra: 013c08065f2860bdfcb482fa13347b5ea324b73bde4c054fc6f397e572ce91d2f202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae29b1d2c9b966b35644bea3e2f6a77171a0d982c0a60a126e39209b2c7bb9dc 0.600000000000 1452081 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": 991755, "vin": [ { "gen": { "height": 991745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae29b1d2c9b966b35644bea3e2f6a77171a0d982c0a60a126e39209b2c7bb9dc" } } ], "extra": [ 1, 60, 8, 6, 95, 40, 96, 189, 252, 180, 130, 250, 19, 52, 123, 94, 163, 36, 183, 59, 222, 76, 5, 79, 198, 243, 151, 229, 114, 206, 145, 210, 242, 2, 17, 0, 0, 0, 1, 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