← previous blocknext block →recent activity
Analyzing
Block #101,990,832
14 transactions · 14 stateful · 2026-09-04 20:05:29 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,990,832 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w210w011w112w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x024b482b…16b0
0x34b655…2a6f
6 touches
3 conflicts
0x29bbfffb…ea4a
0x34b655…2a6f
6 touches
3 conflicts
0x5363946e…9f68
0x34b655…2a6f
6 touches
3 conflicts
0x5eca016a…65e6
0x34b655…2a6f
6 touches
3 conflicts
0xee46716c…d788
0x34b655…2a6f
6 touches
3 conflicts
0x8e10b110…c501
0x34b655…2a6f
4 touches
1 conflict
0x33f541aa…fd33
0x34b655…2a6f
4 touches
1 conflict
0x492dfcee…984c
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
3 conflicts on slot 0x024b482b0a…2616b0
Audit this contract →
← previous block·next block →recent activity