Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a0c731359f102b3f36f087fbc45d28e7bf5630b15cdbb250ec05b4a68fe58c9

Tx prefix hash: 036a6dfc666302fb163b25725e416f88f5e39954ca74d40163d2aae7cdb9faf8
Tx public key: 94cad4f159ec0f18862b0efef241122ef436abdc9b8a77522fff8a9f40275e57
Timestamp: 1669479732 Timestamp [UCT]: 2022-11-26 16:22:12 Age [y:d:h:m:s]: 02:031:23:19:21
Block: 639612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544772 RingCT/type: yes/0
Extra: 0194cad4f159ec0f18862b0efef241122ef436abdc9b8a77522fff8a9f40275e57021100000004e6d27f9c000000000000000000

1 output(s) for total of 4.663370598000 dcy

stealth address amount amount idx
00: 07367eb2504fd0e45c169f07987164bdfa925808405f84f5cc967da01ef28e8e 4.663370598000 1079277 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": 639622, "vin": [ { "gen": { "height": 639612 } } ], "vout": [ { "amount": 4663370598, "target": { "key": "07367eb2504fd0e45c169f07987164bdfa925808405f84f5cc967da01ef28e8e" } } ], "extra": [ 1, 148, 202, 212, 241, 89, 236, 15, 24, 134, 43, 14, 254, 242, 65, 18, 46, 244, 54, 171, 220, 155, 138, 119, 82, 47, 255, 138, 159, 64, 39, 94, 87, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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