← previous blocknext block →recent activity
Analyzing
Block #100,081,594
28 transactions · 21 stateful · 2026-08-29 03:51:07 UTC
Parallelism
89/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,081,594 · 28 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
4w05w16w29w015w116w217w118w122w025w126w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10abefc9…c9bc
0x2b46c0…1669
6 touches
3 conflicts
0x10d80fee…dbda
0x2b46c0…1669
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x1d10f24a…2fb8
0xa6afd3…d132
6 touches
3 conflicts
0x40970e69…da50
0x2b46c0…1669
6 touches
3 conflicts
0x71717491…10cf
0xa6afd3…d132
6 touches
3 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
6 touches
3 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
6 touches
3 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: 0x2b46c08c…ec1669
3 conflicts on slot 0x10abefc9eb…c5c9bc
Audit this contract →
← previous block·next block →recent activity