Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3d64bdf15be930c292d468bde0801b46dbbe683be378555e353675b1e83021e

Tx prefix hash: 8127daa3a1087ad1f2d6e99cc8e1b4e1e13beca438c513ac9d2035b12b11071b
Tx public key: 5f479e5f8818acd7005a16d65a4838706b4c070e00e3c2ccf7aa3a1ee112e356
Timestamp: 1707719188 Timestamp [UCT]: 2024-02-12 06:26:28 Age [y:d:h:m:s]: 00:347:11:52:58
Block: 955734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248716 RingCT/type: yes/0
Extra: 015f479e5f8818acd7005a16d65a4838706b4c070e00e3c2ccf7aa3a1ee112e35602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05863c4eadaf61479e8158b23227c47aa96754184ee56a0091f12858dac5bdb5 0.600000000000 1415032 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": 955744, "vin": [ { "gen": { "height": 955734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05863c4eadaf61479e8158b23227c47aa96754184ee56a0091f12858dac5bdb5" } } ], "extra": [ 1, 95, 71, 158, 95, 136, 24, 172, 215, 0, 90, 22, 214, 90, 72, 56, 112, 107, 76, 7, 14, 0, 227, 194, 204, 247, 170, 58, 30, 225, 18, 227, 86, 2, 17, 0, 0, 0, 2, 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