← previous blocknext block →recent activity
Analyzing
Block #83,199,067
11 transactions · 8 stateful · 2026-06-23 15:48:54 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,199,067 · 11 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
3w05w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x619f5683…5bd4
0x34b655…2a6f
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x9ac79c76…c4a9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1fe3ac7f…7f94
0x065c9d…c394
2 touches
0 conflicts
0x7ac0c8b2…b4f2
0x065c9d…c394
2 touches
0 conflicts
0x9bff759c…e4fe
0x065c9d…c394
2 touches
0 conflicts
0xb651c93e…ed15
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 0x619f5683ba…f75bd4
Audit this contract →
← previous block·next block →recent activity