← previous blocknext block →recent activity
Analyzing
Block #99,133,732
19 transactions · 19 stateful · 2026-08-25 20:06:12 UTC
Parallelism
89/100
Blocked
26%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,133,732 · 19 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
1w05w06w17w111w013w114w015w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe67c5edc…5875
0x8964d7…10f8
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0xe67c5edc…586e
0x8964d7…10f8
4 touches
1 conflict
0xe67c5edc…586f
0x8964d7…10f8
4 touches
1 conflict
0xe67c5edc…5872
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 0xe67c5edce4…455875
Audit this contract →
← previous block·next block →recent activity