← previous blocknext block →recent activity
Analyzing
Block #83,640,240
16 transactions · 14 stateful · 2026-06-25 16:54:46 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,640,240 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w28w09w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffb1ee54…7c2c
0x34b655…2a6f
8 touches
6 conflicts
0x93641233…06f5
0x34b655…2a6f
8 touches
6 conflicts
0xda5e0705…ecb9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0x8b5a6d1a…0062
0x34b655…2a6f
4 touches
1 conflict
0xb1c67a7d…b9b1
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xffb1ee5457…d07c2c
Audit this contract →
← previous block·next block →recent activity