← previous blocknext block →recent activity
Analyzing
Block #100,600,249
21 transactions · 19 stateful · 2026-08-30 23:24:56 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,600,249 · 21 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
1w04w06w17w29w012w113w115w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x92f41d1f…4258
0xa6afd3…d132
6 touches
3 conflicts
0x18c53a40…8bd0
0x34b655…2a6f
4 touches
1 conflict
0x02373c43…3cb3
0x34b655…2a6f
4 touches
1 conflict
0x40f0cbff…df7c
0x34b655…2a6f
4 touches
1 conflict
0xbca4de0c…577c
0x34b655…2a6f
4 touches
1 conflict
0xd75703c7…0b29
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity