← previous blocknext block →recent activity
Analyzing
Block #99,859,833
53 transactions · 43 stateful · 2026-08-28 09:14:09 UTC
Parallelism
74/100
Blocked
63%
Avg conflicts / tx
2.3
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #99,859,833 · 53 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w08w19w211w012w118w320w222w023w125w226w327w428w529w630w731w832w933w1034w1135w1236w1337w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
28 touches
91 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xdfda089f…747f
0x3bd359…433a
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
91 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity