← previous blocknext block →recent activity
Analyzing
Block #99,618,888
17 transactions · 17 stateful · 2026-08-27 12:54:34 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,618,888 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w110w011w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb856d1a1…1f18
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x252ab159…6029
0x34b655…2a6f
2 touches
0 conflicts
0x470b41f6…fc68
0x34b655…2a6f
2 touches
0 conflicts
0x57f8b1c8…badc
0x34b655…2a6f
2 touches
0 conflicts
0x5f2cf00e…8604
0x34b655…2a6f
2 touches
0 conflicts
0x6419eb11…3680
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xb856d1a127…bf1f18
Audit this contract →
← previous block·next block →recent activity