Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ec1c2d9030dc24aaec2d323716e303dd7d5019db4f4cdf9a36fc90cecab79f7

Tx prefix hash: 7aad5ddd22ec98912e9be239d5f16286dca9d0b3aff5f635a25c2d6b6567e636
Tx public key: c56430218c4ef265ba8985423fa89e043a59472cb5c2be84414b1b50c22f2dec
Timestamp: 1705863439 Timestamp [UCT]: 2024-01-21 18:57:19 Age [y:d:h:m:s]: 01:093:00:59:42
Block: 940327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327603 RingCT/type: yes/0
Extra: 01c56430218c4ef265ba8985423fa89e043a59472cb5c2be84414b1b50c22f2dec0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47483b013fd069e31ab24333aa4e81fc4989be2e6f4ee7eb49871dc01d9440e5 0.600000000000 1398463 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": 940337, "vin": [ { "gen": { "height": 940327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47483b013fd069e31ab24333aa4e81fc4989be2e6f4ee7eb49871dc01d9440e5" } } ], "extra": [ 1, 197, 100, 48, 33, 140, 78, 242, 101, 186, 137, 133, 66, 63, 168, 158, 4, 58, 89, 71, 44, 181, 194, 190, 132, 65, 75, 27, 80, 194, 47, 45, 236, 2, 17, 0, 0, 0, 4, 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