← previous blocknext block →recent activity
Analyzing
Block #101,087,433
17 transactions · 17 stateful · 2026-09-01 16:16:29 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,087,433 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w17w210w312w313w415w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xedee7e09…6888
0x34b655…2a6f
6 touches
3 conflicts
0x69e7440f…4b7f
0x34b655…2a6f
4 touches
1 conflict
0xa5a233a4…fd0f
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x336486a4…20bd
0x34b655…2a6f
4 touches
1 conflict
0xfcd7574f…a3a2
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity