← previous blocknext block →recent activity
Analyzing
Block #100,048,197
11 transactions · 11 stateful · 2026-08-29 01:03:00 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,048,197 · 11 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
1w05w06w17w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3686740…a19a
0x34b655…2a6f
6 touches
3 conflicts
0xb839a1e8…22b3
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x32e6354f…5f73
0x34b655…2a6f
2 touches
0 conflicts
0x6a26eb13…b01c
0x34b655…2a6f
2 touches
0 conflicts
0x71d6628b…c9cd
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
3 conflicts on slot 0xa3686740fc…96a19a
Audit this contract →
← previous block·next block →recent activity