Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3fb7867d5a5799c7a075df97d896c709ff0c0a8dc4b98af8edc2a4be9dc12dd

Tx prefix hash: ba8cd10ed26e37aa8ec8f7556535a43faaf33fac958af00c06b5e10287dd724f
Tx public key: d4d494e522d1c79b208bcb62fd0fd80ed99ea40b1b52cddc9597c8b7f897ba99
Timestamp: 1627746873 Timestamp [UCT]: 2021-07-31 15:54:33 Age [y:d:h:m:s]: 03:117:14:54:51
Block: 304584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 856645 RingCT/type: yes/0
Extra: 01d4d494e522d1c79b208bcb62fd0fd80ed99ea40b1b52cddc9597c8b7f897ba9902110000002601f1e57f000000000000000000

1 output(s) for total of 60.087931371000 dcy

stealth address amount amount idx
00: 11fafe0d67dca0f1e47a806556fdb2975981e638e87851ae3cf708d185eb5072 60.087931371000 635477 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": 304594, "vin": [ { "gen": { "height": 304584 } } ], "vout": [ { "amount": 60087931371, "target": { "key": "11fafe0d67dca0f1e47a806556fdb2975981e638e87851ae3cf708d185eb5072" } } ], "extra": [ 1, 212, 212, 148, 229, 34, 209, 199, 155, 32, 139, 203, 98, 253, 15, 216, 14, 217, 158, 164, 11, 27, 82, 205, 220, 149, 151, 200, 183, 248, 151, 186, 153, 2, 17, 0, 0, 0, 38, 1, 241, 229, 127, 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