← previous blocknext block →recent activity
Analyzing
Block #100,872,840
17 transactions · 14 stateful · 2026-08-31 22:16:35 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,872,840 · 17 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
5w010w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b3eb43a…ca08
0x34b655…2a6f
4 touches
1 conflict
0x704bbb0a…892e
0x34b655…2a6f
4 touches
1 conflict
0x55010ec8…ea31
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
0x34b655…2a6f
2 touches
0 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
2 touches
0 conflicts
0x13807d54…85db
0x34b655…2a6f
2 touches
0 conflicts
0x67416d5b…326a
0x34b655…2a6f
2 touches
0 conflicts
0x8f63fda5…b877
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 0x0b3eb43a8c…52ca08
Audit this contract →
← previous block·next block →recent activity