Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fc86ca6511973572a6d5e7dc7ed19e212b7afe1f390b17ae7bf37e875a84830

Tx prefix hash: 49363d5f7826cb9a0791a7e2850a3814c4dc8ac2002c87ccbfd85f97d23506ec
Tx public key: 950c079cf8410acd8e8632a6ccaf3d5205fcd7f74264a3e881abd5ce0c7ac54e
Timestamp: 1711487622 Timestamp [UCT]: 2024-03-26 21:13:42 Age [y:d:h:m:s]: 01:049:01:34:22
Block: 987013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296038 RingCT/type: yes/0
Extra: 01950c079cf8410acd8e8632a6ccaf3d5205fcd7f74264a3e881abd5ce0c7ac54e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 524480c8991a92404926aaacb97e46f9951e239638aee3a7ad63ef8adc2db241 0.600000000000 1447252 of 15

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": 987023, "vin": [ { "gen": { "height": 987013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "524480c8991a92404926aaacb97e46f9951e239638aee3a7ad63ef8adc2db241" } } ], "extra": [ 1, 149, 12, 7, 156, 248, 65, 10, 205, 142, 134, 50, 166, 204, 175, 61, 82, 5, 252, 215, 247, 66, 100, 163, 232, 129, 171, 213, 206, 12, 122, 197, 78, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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