← previous blocknext block →recent activity
Analyzing
Block #107,824,163
14 transactions · 10 stateful · 2026-09-25 06:41:50 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,824,163 · 14 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
2w03w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57b62287…9ae4
0x34b655…2a6f
4 touches
1 conflict
0xdcd07321…1c31
0x34b655…2a6f
4 touches
1 conflict
0xa7ba83b5…d0a8
0x34b655…2a6f
4 touches
1 conflict
0x3243e72f…1f6d
0x34b655…2a6f
2 touches
0 conflicts
0x3c9b10c1…d791
0x34b655…2a6f
2 touches
0 conflicts
0x4a45b318…9716
0x34b655…2a6f
2 touches
0 conflicts
0x5969523e…5191
0x34b655…2a6f
2 touches
0 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
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 0x57b62287b9…249ae4
Audit this contract →
← previous block·next block →recent activity