Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: effcb64ee66d49fb9358990ab19a8587c2c4def3a27dd1f50b48e6772d391970

Tx prefix hash: e0dd3675bbea54c01d0ebd4de514f9edffac16e1cb6561b77ad4cacc3eeb2022
Tx public key: e376d4c0dcc9ed6f9f18ae733bc2459f369e7317bd777629e271526ef04ed821
Timestamp: 1726153794 Timestamp [UCT]: 2024-09-12 15:09:54 Age [y:d:h:m:s]: 00:101:13:01:08
Block: 1108567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72653 RingCT/type: yes/0
Extra: 01e376d4c0dcc9ed6f9f18ae733bc2459f369e7317bd777629e271526ef04ed82102110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7e1447921dcbb4d2971c16f197c4c88c9062b43d64fc72314ef6c1b829c64b8 0.600000000000 1586510 of 15

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": 1108577, "vin": [ { "gen": { "height": 1108567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7e1447921dcbb4d2971c16f197c4c88c9062b43d64fc72314ef6c1b829c64b8" } } ], "extra": [ 1, 227, 118, 212, 192, 220, 201, 237, 111, 159, 24, 174, 115, 59, 194, 69, 159, 54, 158, 115, 23, 189, 119, 118, 41, 226, 113, 82, 110, 240, 78, 216, 33, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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