Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 119cedacc97948213d8a38fd7e5a316ada5638b70ecdc29c7f7c911315d03c70

Tx prefix hash: c861569d10f71f950fa975379787b0d33094f9273c1c5d3de45cef9943f9c982
Tx public key: 4d2686fd9a6a332437903fc9d714dc1ee53dc84a65f54258ff0588d655fd34bb
Timestamp: 1675452335 Timestamp [UCT]: 2023-02-03 19:25:35 Age [y:d:h:m:s]: 01:350:18:59:44
Block: 689117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511645 RingCT/type: yes/0
Extra: 014d2686fd9a6a332437903fc9d714dc1ee53dc84a65f54258ff0588d655fd34bb0211000000015029cbac000000000000000000

1 output(s) for total of 3.196459765000 dcy

stealth address amount amount idx
00: 88933bbbc2e4d1e3e1a47ea0ee89a0058063971d821705ee226303b84fa154a3 3.196459765000 1131781 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": 689127, "vin": [ { "gen": { "height": 689117 } } ], "vout": [ { "amount": 3196459765, "target": { "key": "88933bbbc2e4d1e3e1a47ea0ee89a0058063971d821705ee226303b84fa154a3" } } ], "extra": [ 1, 77, 38, 134, 253, 154, 106, 51, 36, 55, 144, 63, 201, 215, 20, 220, 30, 229, 61, 200, 74, 101, 245, 66, 88, 255, 5, 136, 214, 85, 253, 52, 187, 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