← previous blocknext block →recent activity
Analyzing
Block #83,623,523
15 transactions · 15 stateful · 2026-06-25 15:03:06 UTC
Parallelism
87/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,623,523 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w09w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x785889c9…0603
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfd4e2262…cd8c
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0b16149e…7d4d
0x065c9d…c394
2 touches
0 conflicts
0x2bc7d2ff…a60e
0x065c9d…c394
2 touches
0 conflicts
0x94665f2c…2038
0x065c9d…c394
2 touches
0 conflicts
0xf34b064e…6ff5
0x065c9d…c394
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0x785889c9fb…160603
Audit this contract →
← previous block·next block →recent activity