← previous blocknext block →recent activity
Analyzing
Block #101,024,831
31 transactions · 29 stateful · 2026-09-01 11:01:13 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.06
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #101,024,831 · 31 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w16w27w08w110w311w112w415w016w118w519w622w724w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41c56387…a8f6
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xf65c9ad4…88f7
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x4a1bde21…1a62
0x34b655…2a6f
4 touches
1 conflict
0x4ec687a7…7f1e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
15 conflicts on slot 0x41c5638713…86a8f6
Audit this contract →
← previous block·next block →recent activity