Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 204d9eda13ea10bfa3c8018add2abc9b2f9c4134d39a32c0b28654bad3b49176

Tx prefix hash: 524c229ae5667687cb9003f22d3231a74d180c71a2d3fb094aa38c51d4a4ab59
Tx public key: 7b5ca1f414e618d2c6c11db08faf0e0d931ab803bbd5dbebbe4b5a3619803232
Timestamp: 1649289875 Timestamp [UCT]: 2022-04-07 00:04:35 Age [y:d:h:m:s]: 03:021:13:18:52
Block: 474755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 795854 RingCT/type: yes/0
Extra: 017b5ca1f414e618d2c6c11db08faf0e0d931ab803bbd5dbebbe4b5a36198032320211000000034da16a3a000000000000000000

1 output(s) for total of 16.403625563000 dcy

stealth address amount amount idx
00: aa78579ca5b5a5f6ecf011d316a24951e76997107cdb39565f1665a4e007edf1 16.403625563000 894862 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": 474765, "vin": [ { "gen": { "height": 474755 } } ], "vout": [ { "amount": 16403625563, "target": { "key": "aa78579ca5b5a5f6ecf011d316a24951e76997107cdb39565f1665a4e007edf1" } } ], "extra": [ 1, 123, 92, 161, 244, 20, 230, 24, 210, 198, 193, 29, 176, 143, 175, 14, 13, 147, 26, 184, 3, 187, 213, 219, 235, 190, 75, 90, 54, 25, 128, 50, 50, 2, 17, 0, 0, 0, 3, 77, 161, 106, 58, 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