Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2d873cbb0d5bed7ae7bea092a46538028274bef07e689d921c18c058ae46476

Tx prefix hash: 5560bf58e29595d4a7e079f499314730544bec91e9092a9c7b95759980309636
Tx public key: 2c32814de8a1df4d9e4df8bff360f297748a690532eeafe53d3c87917a8486ad
Timestamp: 1658048714 Timestamp [UCT]: 2022-07-17 09:05:14 Age [y:d:h:m:s]: 03:106:15:55:25
Block: 545614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 855982 RingCT/type: yes/0
Extra: 012c32814de8a1df4d9e4df8bff360f297748a690532eeafe53d3c87917a8486ad021100000001c9067537000000000000000000

1 output(s) for total of 9.553322999000 dcy

stealth address amount amount idx
00: d0a4cb8c0ea222b8dc1cd4fe9a10e0b4f5d3582e94d11f3ec5ccd06aad0f76c0 9.553322999000 976535 of 0

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": 545624, "vin": [ { "gen": { "height": 545614 } } ], "vout": [ { "amount": 9553322999, "target": { "key": "d0a4cb8c0ea222b8dc1cd4fe9a10e0b4f5d3582e94d11f3ec5ccd06aad0f76c0" } } ], "extra": [ 1, 44, 50, 129, 77, 232, 161, 223, 77, 158, 77, 248, 191, 243, 96, 242, 151, 116, 138, 105, 5, 50, 238, 175, 229, 61, 60, 135, 145, 122, 132, 134, 173, 2, 17, 0, 0, 0, 1, 201, 6, 117, 55, 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