← previous blocknext block →recent activity
Analyzing
Block #100,588,122
21 transactions · 18 stateful · 2026-08-30 22:23:56 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,588,122 · 21 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
1w02w14w05w16w27w314w116w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81716ce9…095f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb86
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x08be6a43…f4dc
0x34b655…2a6f
4 touches
1 conflict
0x0e3b59e9…d9d0
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 0x81716ce924…61095f
Audit this contract →
← previous block·next block →recent activity