← previous blocknext block →recent activity
Analyzing
Block #99,361,772
21 transactions · 20 stateful · 2026-08-26 15:13:39 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,361,772 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w07w29w313w014w116w119w020w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6174640…66c9
0x851145…3f07
4 touches
1 conflict
0xeabd47a7…c286
0x851145…3f07
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x7d4f80a4…bb19
0x1b6862…e19c
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: 0x851145ea…9f3f07
1 conflict on slot 0xc617464050…2c66c9
Audit this contract →
← previous block·next block →recent activity