Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2a2a740013180d21f74065272bc01e9eab119aa4ea59e76d060cc11fbbc6341

Tx prefix hash: 1995e0a2bbbb6643de756095af15bbbd6fb1c08bd252ee881b62e14ebb9dd0fe
Tx public key: f16b8072738a8aea7400363d9acd3f184b834e9ffc935acd42307ac6c45f6266
Timestamp: 1675153859 Timestamp [UCT]: 2023-01-31 08:30:59 Age [y:d:h:m:s]: 02:078:00:53:12
Block: 686632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 577417 RingCT/type: yes/0
Extra: 01f16b8072738a8aea7400363d9acd3f184b834e9ffc935acd42307ac6c45f62660211000000015029cbac000000000000000000

1 output(s) for total of 3.257639950000 dcy

stealth address amount amount idx
00: d34a5d53f8f92e3acd41ee92d954db41c1370836485c4f59ebcb41c1e4078bb3 3.257639950000 1129141 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": 686642, "vin": [ { "gen": { "height": 686632 } } ], "vout": [ { "amount": 3257639950, "target": { "key": "d34a5d53f8f92e3acd41ee92d954db41c1370836485c4f59ebcb41c1e4078bb3" } } ], "extra": [ 1, 241, 107, 128, 114, 115, 138, 138, 234, 116, 0, 54, 61, 154, 205, 63, 24, 75, 131, 78, 159, 252, 147, 90, 205, 66, 48, 122, 198, 196, 95, 98, 102, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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