Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35558f2166f5ef924da6d42b4c3c8d4c87f5be67063a9bcbd8118244088ab585

Tx prefix hash: fd38d808b89b13f136ec43bd6e48d92bee75f4eb0b27e75bf47f080da739f3f9
Tx public key: 76d7dfbe864ff5e2b463cc9131acc3f9a2619d08da0ce9adc14daa9c0decf384
Timestamp: 1681197809 Timestamp [UCT]: 2023-04-11 07:23:29 Age [y:d:h:m:s]: 01:357:20:28:04
Block: 736104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517040 RingCT/type: yes/0
Extra: 0176d7dfbe864ff5e2b463cc9131acc3f9a2619d08da0ce9adc14daa9c0decf384021100000001b3164c24000000000000000000

1 output(s) for total of 2.233480166000 dcy

stealth address amount amount idx
00: 9a58f5270f6535f47f540837b110874b19e1a93c1716bff669f27128442e1c86 2.233480166000 1182501 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": 736114, "vin": [ { "gen": { "height": 736104 } } ], "vout": [ { "amount": 2233480166, "target": { "key": "9a58f5270f6535f47f540837b110874b19e1a93c1716bff669f27128442e1c86" } } ], "extra": [ 1, 118, 215, 223, 190, 134, 79, 245, 226, 180, 99, 204, 145, 49, 172, 195, 249, 162, 97, 157, 8, 218, 12, 233, 173, 193, 77, 170, 156, 13, 236, 243, 132, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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