Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21e94539e358c2c0ba5deba2bb74bfa251d2074b7928af7132d9233fcd68c911

Tx prefix hash: d5853fa1dade312fddf85c374e50349984e3da0c47c9198e6d7d4c6b90a2e50e
Tx public key: 8cfd940315b9a62975e1bf0f5f10ba7ce626be46ec3c41a0b925bc82753aec44
Timestamp: 1713284667 Timestamp [UCT]: 2024-04-16 16:24:27 Age [y:d:h:m:s]: 00:314:20:05:33
Block: 1001863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225071 RingCT/type: yes/0
Extra: 018cfd940315b9a62975e1bf0f5f10ba7ce626be46ec3c41a0b925bc82753aec4402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a74853d09589c754c22150c81e7a65e0a404c1bc989321b8430f23a0e6075935 0.600000000000 1462375 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": 1001873, "vin": [ { "gen": { "height": 1001863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a74853d09589c754c22150c81e7a65e0a404c1bc989321b8430f23a0e6075935" } } ], "extra": [ 1, 140, 253, 148, 3, 21, 185, 166, 41, 117, 225, 191, 15, 95, 16, 186, 124, 230, 38, 190, 70, 236, 60, 65, 160, 185, 37, 188, 130, 117, 58, 236, 68, 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