← previous blocknext block →recent activity
Analyzing
Block #100,140,153
16 transactions · 15 stateful · 2026-08-29 08:46:06 UTC
Parallelism
81/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,140,153 · 16 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
10w011w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffab12e1…4dcb
0x8964d7…10f8
6 touches
3 conflicts
0xffab12e1…4dcc
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0xffab12e1…4dcf
0x8964d7…10f8
6 touches
3 conflicts
0xffab12e1…4dd0
0x8964d7…10f8
6 touches
3 conflicts
0x9a393b63…7298
0x8964d7…10f8
4 touches
1 conflict
0x9a393b63…729b
0x8964d7…10f8
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: 0x8964d7c9…5b10f8
3 conflicts on slot 0xffab12e106…3d4dcb
Audit this contract →
← previous block·next block →recent activity