← previous blocknext block →recent activity
Analyzing
Block #101,937,351
12 transactions · 11 stateful · 2026-09-04 15:34:11 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,937,351 · 12 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
2w04w06w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x9ad6236d…7710
0x34b655…2a6f
4 touches
1 conflict
0xfaf5fe80…1ffc
0x34b655…2a6f
4 touches
1 conflict
0x2c539d94…b63a
0x34b655…2a6f
4 touches
1 conflict
0x00ee16c8…ef57
0x34b655…2a6f
4 touches
1 conflict
0x460ccb65…17a8
0x34b655…2a6f
2 touches
0 conflicts
0x60a536a6…ef7a
0x34b655…2a6f
2 touches
0 conflicts
0x764c3e36…c6db
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity