Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8abe36076c9c074b494ddd9c3427e29b7f52047537be8513bd7b3397489577f2

Tx prefix hash: 3bb1bbc818ba85d506ab53d8bcc80453c17cea41649a4ce255b9c676cac13f7d
Tx public key: 2f76d38409b487fe4e066afd6856576f59eb946e759b2986f194bcbe86a46cdf
Timestamp: 1696635223 Timestamp [UCT]: 2023-10-06 23:33:43 Age [y:d:h:m:s]: 01:185:23:03:01
Block: 864049 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393949 RingCT/type: yes/0
Extra: 012f76d38409b487fe4e066afd6856576f59eb946e759b2986f194bcbe86a46cdf02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.841486233000 dcy

stealth address amount amount idx
00: 0a09423f42caf0f540bbe696079360f5b42b5b2a114c364fb43b1c67a9dbc3d9 0.841486233000 1318555 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": 864059, "vin": [ { "gen": { "height": 864049 } } ], "vout": [ { "amount": 841486233, "target": { "key": "0a09423f42caf0f540bbe696079360f5b42b5b2a114c364fb43b1c67a9dbc3d9" } } ], "extra": [ 1, 47, 118, 211, 132, 9, 180, 135, 254, 78, 6, 106, 253, 104, 86, 87, 111, 89, 235, 148, 110, 117, 155, 41, 134, 241, 148, 188, 190, 134, 164, 108, 223, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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