Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 045ccd942fe71004411c717064961c8c6211c56c55c638c22ed1d74338b8b702

Tx prefix hash: 8733e4484a27fa6b23eb86c7b964b2b38ca0ac6da09854e5e4eb6a1e6aae1a31
Tx public key: d9a71a1963a4ad4658759fcbdbdd99e68b618e6a61209e85e21aeb79ad07596f
Timestamp: 1693599515 Timestamp [UCT]: 2023-09-01 20:18:35 Age [y:d:h:m:s]: 01:131:23:44:03
Block: 838859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355675 RingCT/type: yes/0
Extra: 01d9a71a1963a4ad4658759fcbdbdd99e68b618e6a61209e85e21aeb79ad07596f021100000005faf35c9c000000000000000000

1 output(s) for total of 1.019792888000 dcy

stealth address amount amount idx
00: 65b53c60e7abd0815d78bda201c5b831c0de5a149d0148d6672bc75167e1ec2c 1.019792888000 1291649 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": 838869, "vin": [ { "gen": { "height": 838859 } } ], "vout": [ { "amount": 1019792888, "target": { "key": "65b53c60e7abd0815d78bda201c5b831c0de5a149d0148d6672bc75167e1ec2c" } } ], "extra": [ 1, 217, 167, 26, 25, 99, 164, 173, 70, 88, 117, 159, 203, 219, 221, 153, 230, 139, 97, 142, 106, 97, 32, 158, 133, 226, 26, 235, 121, 173, 7, 89, 111, 2, 17, 0, 0, 0, 5, 250, 243, 92, 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