← previous blocknext block →recent activity
Analyzing
Block #99,090,414
52 transactions · 47 stateful · 2026-08-25 16:28:06 UTC
Parallelism
81/100
Blocked
66%
Avg conflicts / tx
1.87
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,090,414 · 52 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w27w08w010w012w113w314w116w017w118w219w320w421w522w623w724w826w127w232w141w142w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xa02838a3…bc54
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x36743f6f…476b
0x3bd359…433a
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
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: 0xf5b5f7f8…a36d70
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity