Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eaed886b55c2b3beea994053c24140282fced6d26e1f066523f4d73748c5b76

Tx prefix hash: b783d5060b360a0b66cf3adf4106cb833fef41cbb4223dccf56511ae1c0031d2
Tx public key: f02fbbb75579013e3babd21e40096ed91268a4372ad2680f1fca1fba4df29c01
Timestamp: 1581090334 Timestamp [UCT]: 2020-02-07 15:45:34 Age [y:d:h:m:s]: 04:326:01:19:06
Block: 60633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124510 RingCT/type: yes/0
Extra: 01f02fbbb75579013e3babd21e40096ed91268a4372ad2680f1fca1fba4df29c0102110000000256c366d3000000000000000000

1 output(s) for total of 386.454633228000 dcy

stealth address amount amount idx
00: 8f124151ba6ef576e8144eea442aa0dbd3ac2b19d2fee9c43d2669e78b6daeca 386.454633228000 111661 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": 60643, "vin": [ { "gen": { "height": 60633 } } ], "vout": [ { "amount": 386454633228, "target": { "key": "8f124151ba6ef576e8144eea442aa0dbd3ac2b19d2fee9c43d2669e78b6daeca" } } ], "extra": [ 1, 240, 47, 187, 183, 85, 121, 1, 62, 59, 171, 210, 30, 64, 9, 110, 217, 18, 104, 164, 55, 42, 210, 104, 15, 31, 202, 31, 186, 77, 242, 156, 1, 2, 17, 0, 0, 0, 2, 86, 195, 102, 211, 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