Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19944526d1b8058752ac5089e7e1d5fb2957c47ea9c38e93a6ca0b769cfd9548

Tx prefix hash: e2952cc9118a86f2b09a3d205be77f596995e5f6ccbda8b4854574b1a3447088
Tx public key: 750463612e671826a59e33c0e813acf8afb778e0d61029f6fbf605c15148ee56
Timestamp: 1712708651 Timestamp [UCT]: 2024-04-10 00:24:11 Age [y:d:h:m:s]: 00:218:23:30:43
Block: 997084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156790 RingCT/type: yes/0
Extra: 01750463612e671826a59e33c0e813acf8afb778e0d61029f6fbf605c15148ee5602110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbb5b2a8b4a39e079230b0742cec943923ce4ea8f18712526fb49885edbb20df 0.600000000000 1457512 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": 997094, "vin": [ { "gen": { "height": 997084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbb5b2a8b4a39e079230b0742cec943923ce4ea8f18712526fb49885edbb20df" } } ], "extra": [ 1, 117, 4, 99, 97, 46, 103, 24, 38, 165, 158, 51, 192, 232, 19, 172, 248, 175, 183, 120, 224, 214, 16, 41, 246, 251, 246, 5, 193, 81, 72, 238, 86, 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