← previous blocknext block →recent activity
Analyzing
Block #100,026,605
12 transactions · 11 stateful · 2026-08-28 23:14:18 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,026,605 · 12 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
0xd1b40f29…9b9d
0x34b655…2a6f
4 touches
1 conflict
0x743f0e02…73ec
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
2 touches
0 conflicts
0x1a3d2527…8ca0
0x34b655…2a6f
2 touches
0 conflicts
0x327c57dd…836d
0x34b655…2a6f
2 touches
0 conflicts
0x422890a1…7460
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 0xd1b40f2924…ae9b9d
Audit this contract →
← previous block·next block →recent activity