Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52d71a9133c8ebd5900b94c8afdc9c350eb068973458917d3a922f3fd3883473

Tx prefix hash: 2a206fcb396973a05b1aff8ced5247a32337801e35601d9d52f18fcc4fcf0c9a
Tx public key: 852ce6159b4e379be1a2447bf1850eccd5e0aa4c5fdd77022d6855f8292721fb
Timestamp: 1674111163 Timestamp [UCT]: 2023-01-19 06:52:43 Age [y:d:h:m:s]: 02:125:16:24:31
Block: 677974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 611530 RingCT/type: yes/0
Extra: 01852ce6159b4e379be1a2447bf1850eccd5e0aa4c5fdd77022d6855f8292721fb021100000001e7ace25d000000000000000000

1 output(s) for total of 3.480091343000 dcy

stealth address amount amount idx
00: 08aa43c7f36db1e2b779e6d1f5b56443369fab02d9e7c656d67028cd4012fe21 3.480091343000 1119777 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": 677984, "vin": [ { "gen": { "height": 677974 } } ], "vout": [ { "amount": 3480091343, "target": { "key": "08aa43c7f36db1e2b779e6d1f5b56443369fab02d9e7c656d67028cd4012fe21" } } ], "extra": [ 1, 133, 44, 230, 21, 155, 78, 55, 155, 225, 162, 68, 123, 241, 133, 14, 204, 213, 224, 170, 76, 95, 221, 119, 2, 45, 104, 85, 248, 41, 39, 33, 251, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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