← previous blocknext block →recent activity
Analyzing
Block #100,161,880
15 transactions · 15 stateful · 2026-08-29 10:35:29 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,161,880 · 15 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
6w07w19w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b2fc5ca…a0ba
0x34b655…2a6f
4 touches
1 conflict
0xca5b9231…3bd1
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x51087f5a…61f7
0x34b655…2a6f
4 touches
1 conflict
0x52e0faa1…d718
0x34b655…2a6f
4 touches
1 conflict
0x2ad2f4bc…1800
0x34b655…2a6f
4 touches
1 conflict
0xcb45d9d6…cb86
0x1b6862…e19c
2 touches
0 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0x7b2fc5ca9d…cda0ba
Audit this contract →
← previous block·next block →recent activity