← previous blocknext block →recent activity
Analyzing
Block #100,736,832
8 transactions · 6 stateful · 2026-08-31 10:52:00 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,736,832 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ee8b564…4c49
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x41c56387…a8f6
0x34b655…2a6f
2 touches
0 conflicts
0x49890ced…6f23
0x34b655…2a6f
2 touches
0 conflicts
0x4b1874d3…00ff
0x34b655…2a6f
2 touches
0 conflicts
0x4ec687a7…7f1e
0x34b655…2a6f
2 touches
0 conflicts
0x5791c2b1…73d5
0x34b655…2a6f
2 touches
0 conflicts
0xac2a0273…721b
0x34b655…2a6f
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 0x3ee8b5644d…f04c49
Audit this contract →
← previous block·next block →recent activity