Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91adc0045cb0d2b1b76ffde299a5922245da0aa44d0e11a6d24631f4cf2a6ad5

Tx prefix hash: 29aa65ab167b3d0df354b206d2e6f5e7a401332b935f3bf0e9c010be58c312fd
Tx public key: 6f32e8a5998e8857f1aecbae8b10affc8ba297501c8e7774ecd234fbb2887d7c
Timestamp: 1676604290 Timestamp [UCT]: 2023-02-17 03:24:50 Age [y:d:h:m:s]: 01:333:21:35:47
Block: 698670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499581 RingCT/type: yes/0
Extra: 016f32e8a5998e8857f1aecbae8b10affc8ba297501c8e7774ecd234fbb2887d7c02110000000174b6d784000000000000000000

1 output(s) for total of 2.971776701000 dcy

stealth address amount amount idx
00: fb317beb9efee51702aa3db38503859cb4970d3a206af9e748fd995e0040f55c 2.971776701000 1142009 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": 698680, "vin": [ { "gen": { "height": 698670 } } ], "vout": [ { "amount": 2971776701, "target": { "key": "fb317beb9efee51702aa3db38503859cb4970d3a206af9e748fd995e0040f55c" } } ], "extra": [ 1, 111, 50, 232, 165, 153, 142, 136, 87, 241, 174, 203, 174, 139, 16, 175, 252, 139, 162, 151, 80, 28, 142, 119, 116, 236, 210, 52, 251, 178, 136, 125, 124, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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