← previous blocknext block →recent activity
Analyzing
Block #99,354,910
20 transactions · 19 stateful · 2026-08-26 14:39:00 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,354,910 · 20 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
1w02w03w15w16w27w311w012w113w116w217w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9438fc3…f9a2
0x851145…3f07
6 touches
3 conflicts
0xd3c05624…3417
0x34b655…2a6f
6 touches
3 conflicts
0x4c876cb8…bb49
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x44000a8f…8fca
0x851145…3f07
6 touches
3 conflicts
0x4dd2a831…bd5d
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
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: 0x851145ea…9f3f07
3 conflicts on slot 0xd9438fc319…b2f9a2
Audit this contract →
← previous block·next block →recent activity