← previous blocknext block →recent activity
Analyzing
Block #99,289,273
19 transactions · 14 stateful · 2026-08-26 09:08:47 UTC
Parallelism
84/100
Blocked
43%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,289,273 · 19 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
1w05w16w17w08w111w012w113w014w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe251ba03…50f8
0x34b655…2a6f
6 touches
3 conflicts
0x3f2100d8…f9b5
0xa6afd3…d132
4 touches
1 conflict
0x58a50018…5045
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xc2583d5b…be9d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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: Perpl
3 conflicts on slot 0xe251ba03d8…af50f8
Audit this contract →
← previous block·next block →recent activity