← previous blocknext block →recent activity
Analyzing
Block #100,162,101
14 transactions · 12 stateful · 2026-08-29 10:36:36 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,162,101 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w26w38w29w010w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd364942…1404
0x34b655…2a6f
10 touches
10 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0x72083f0d…082a
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x24bb46f7…3853
0x34b655…2a6f
6 touches
3 conflicts
0x7c5c8608…021d
0x34b655…2a6f
4 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7d07e5f7…6703
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
10 conflicts on slot 0xbd364942ce…461404
Audit this contract →
← previous block·next block →recent activity