Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c84cd497a70b305d8b7d0fb77c41a83a55c6bb699b0a61ad664d3bd26d4c8d00

Tx prefix hash: b4433f3621c1260d125a43647765fcc38bd4e388317505c3b4b10e22e34ed6f3
Tx public key: 9fc55321b6b0ee724a2fca6c1d00ac7ec1a9d336b448fe8c24d951d8f46a8876
Timestamp: 1710709006 Timestamp [UCT]: 2024-03-17 20:56:46 Age [y:d:h:m:s]: 00:342:12:30:20
Block: 980551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244853 RingCT/type: yes/0
Extra: 019fc55321b6b0ee724a2fca6c1d00ac7ec1a9d336b448fe8c24d951d8f46a88760211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c49be1a9df709bf88c060e2496afda34d928fc0b03af208efa00622d6f4c69e4 0.600000000000 1440626 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": 980561, "vin": [ { "gen": { "height": 980551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c49be1a9df709bf88c060e2496afda34d928fc0b03af208efa00622d6f4c69e4" } } ], "extra": [ 1, 159, 197, 83, 33, 182, 176, 238, 114, 74, 47, 202, 108, 29, 0, 172, 126, 193, 169, 211, 54, 180, 72, 254, 140, 36, 217, 81, 216, 244, 106, 136, 118, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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