← previous blocknext block →recent activity
Analyzing
Block #101,986,384
10 transactions · 10 stateful · 2026-09-04 19:42:51 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,986,384 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac27d4e9…fffc
0x34b655…2a6f
4 touches
1 conflict
0x4dffc33e…068d
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x14bfb388…e757
0x34b655…2a6f
2 touches
0 conflicts
0x53e08444…d671
0x34b655…2a6f
2 touches
0 conflicts
0x59291d60…d4d1
0x34b655…2a6f
2 touches
0 conflicts
0x65f011a5…bc6e
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 0xac27d4e99a…c3fffc
Audit this contract →
← previous block·next block →recent activity