← previous blocknext block →recent activity
Analyzing
Block #100,587,217
32 transactions · 32 stateful · 2026-08-30 22:19:23 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,587,217 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w16w07w19w010w011w112w213w316w017w118w220w121w128w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0279074…2413
0x8964d7…10f8
6 touches
3 conflicts
0xd0279074…240c
0x8964d7…10f8
6 touches
3 conflicts
0xd0279074…240d
0x8964d7…10f8
6 touches
3 conflicts
0xd0279074…2410
0x8964d7…10f8
6 touches
3 conflicts
0xd0279074…2411
0x8964d7…10f8
6 touches
3 conflicts
0x0b3eb43a…ca08
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x67a56c8b…f955
0x34b655…2a6f
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: 0x8964d7c9…5b10f8
3 conflicts on slot 0xd02790743f…632413
Audit this contract →
← previous block·next block →recent activity