← previous blocknext block →recent activity
Analyzing
Block #99,187,603
49 transactions · 43 stateful · 2026-08-26 00:37:12 UTC
Parallelism
71/100
Blocked
74%
Avg conflicts / tx
2.04
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #99,187,603 · 49 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
1w02w13w25w06w17w010w113w114w215w316w419w221w422w327w328w429w530w431w637w138w243w844w947w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x1ee44aac…e8cc
0x34b655…2a6f
8 touches
6 conflicts
0x8a02d049…f481
0x34b655…2a6f
8 touches
6 conflicts
0x93aea27d…38e0
0x34b655…2a6f
8 touches
6 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: Perpl
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity