← previous blocknext block →recent activity
Analyzing
Block #99,197,201
16 transactions · 16 stateful · 2026-08-26 01:25:30 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,197,201 · 16 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
1w02w14w07w08w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbda015e…6b93
0x8964d7…10f8
4 touches
1 conflict
0xfbda015e…6b8d
0x8964d7…10f8
4 touches
1 conflict
0xfbda015e…6b8e
0x8964d7…10f8
4 touches
1 conflict
0xfbda015e…6b91
0x8964d7…10f8
4 touches
1 conflict
0xfbda015e…6b92
0x8964d7…10f8
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x40afcb37…764e
0x34b655…2a6f
4 touches
1 conflict
0x631b4113…baa9
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: 0x8964d7c9…5b10f8
1 conflict on slot 0xfbda015e97…c56b93
Audit this contract →
← previous block·next block →recent activity