← previous blocknext block →recent activity
Analyzing
Block #99,308,724
18 transactions · 17 stateful · 2026-08-26 10:46:38 UTC
Parallelism
89/100
Blocked
12%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,308,724 · 18 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
3w010w013w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f336d91…d7f4
0x8964d7…10f8
4 touches
1 conflict
0x7f336d91…d7f5
0x8964d7…10f8
4 touches
1 conflict
0x7f336d91…d7f8
0x8964d7…10f8
4 touches
1 conflict
0x7f336d91…d7f9
0x8964d7…10f8
4 touches
1 conflict
0x7f336d91…d7fb
0x8964d7…10f8
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
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
1 conflict on slot 0x7f336d915a…07d7f4
Audit this contract →
← previous block·next block →recent activity