← previous blocknext block →recent activity
Analyzing
Block #101,095,664
10 transactions · 9 stateful · 2026-09-01 16:57:53 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,095,664 · 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
4w05w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa11b60f7…8e8b
0x34b655…2a6f
4 touches
1 conflict
0xbcdd58ff…0711
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6571
0x34b655…2a6f
4 touches
1 conflict
0x9e85f8a1…3f25
0x34b655…2a6f
3 touches
1 conflict
0xeba56708…8cd7
0x34ae4d…3fc5
2 touches
0 conflicts
0x26253352…1a75
0x34b655…2a6f
2 touches
0 conflicts
0x4a45b318…9716
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 0xa11b60f7c7…f88e8b
Audit this contract →
← previous block·next block →recent activity