Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c8a5026b06b3e8b976d81a9954e06e55a797586359e08a9764e7fe64ca19b96

Tx prefix hash: 207530917535b6ead68f07ff64e44b66ab0499ea9a599add0ecfe75eacf18400
Tx public key: dcd2cc5362e90753bbd897deb07f7fab7d390605d9c9a5edf949c9cd183a0085
Timestamp: 1712313760 Timestamp [UCT]: 2024-04-05 10:42:40 Age [y:d:h:m:s]: 01:241:04:23:24
Block: 993808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431105 RingCT/type: yes/0
Extra: 01dcd2cc5362e90753bbd897deb07f7fab7d390605d9c9a5edf949c9cd183a008502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5874e31a2f7c2ffdfd7e4343f83dad0fb8144615c6530cca3c27de7b3506bf91 0.600000000000 1454196 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": 993818, "vin": [ { "gen": { "height": 993808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5874e31a2f7c2ffdfd7e4343f83dad0fb8144615c6530cca3c27de7b3506bf91" } } ], "extra": [ 1, 220, 210, 204, 83, 98, 233, 7, 83, 187, 216, 151, 222, 176, 127, 127, 171, 125, 57, 6, 5, 217, 201, 165, 237, 249, 73, 201, 205, 24, 58, 0, 133, 2, 17, 0, 0, 0, 2, 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