Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a94d1c40b6b5dd5bbe21a9bed047f81cdc15067c5112f147855128bfce24a4a0

Tx prefix hash: 6df16f8d3bcb68a9ce92861941916dab7062604b80818216d0d892d3776ead14
Tx public key: 4659c7def19d4ab2e5d328a1b0454c974151e48a388fc5fa4ab768f30d841c58
Timestamp: 1719168470 Timestamp [UCT]: 2024-06-23 18:47:50 Age [y:d:h:m:s]: 00:268:16:43:52
Block: 1050644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192028 RingCT/type: yes/0
Extra: 014659c7def19d4ab2e5d328a1b0454c974151e48a388fc5fa4ab768f30d841c5802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8f0c86e4a7faf48e582ac09d1b947056b7fede2946d449eed2d971eab88a71b 0.600000000000 1520819 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": 1050654, "vin": [ { "gen": { "height": 1050644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8f0c86e4a7faf48e582ac09d1b947056b7fede2946d449eed2d971eab88a71b" } } ], "extra": [ 1, 70, 89, 199, 222, 241, 157, 74, 178, 229, 211, 40, 161, 176, 69, 76, 151, 65, 81, 228, 138, 56, 143, 197, 250, 74, 183, 104, 243, 13, 132, 28, 88, 2, 17, 0, 0, 0, 1, 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