Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e681ba8044b7d2d36aa92d3dc9d24355fb77c417baa6b6f7df2e298f1663450e

Tx prefix hash: 0b2afcad19613e4da22a5c71aee1e55043bc4272c3a66f0d66eadb76f8579d5a
Tx public key: a664e10f81a5866d68b98d5b2e84c0916ea4d10468fae17a047ac3a9168700ae
Timestamp: 1681364576 Timestamp [UCT]: 2023-04-13 05:42:56 Age [y:d:h:m:s]: 01:294:10:00:04
Block: 737481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471683 RingCT/type: yes/0
Extra: 01a664e10f81a5866d68b98d5b2e84c0916ea4d10468fae17a047ac3a9168700ae0211000000055029cbac000000000000000000

1 output(s) for total of 2.210138681000 dcy

stealth address amount amount idx
00: 31b71b9739f59d3a63b98a8815606b1fa1c5d0ec87b5dfc66a35b7cb7666801c 2.210138681000 1184040 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": 737491, "vin": [ { "gen": { "height": 737481 } } ], "vout": [ { "amount": 2210138681, "target": { "key": "31b71b9739f59d3a63b98a8815606b1fa1c5d0ec87b5dfc66a35b7cb7666801c" } } ], "extra": [ 1, 166, 100, 225, 15, 129, 165, 134, 109, 104, 185, 141, 91, 46, 132, 192, 145, 110, 164, 209, 4, 104, 250, 225, 122, 4, 122, 195, 169, 22, 135, 0, 174, 2, 17, 0, 0, 0, 5, 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