← previous blocknext block →recent activity
Analyzing
Block #99,625,108
25 transactions · 24 stateful · 2026-08-27 13:26:24 UTC
Parallelism
72/100
Blocked
42%
Avg conflicts / tx
0.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,625,108 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w28w09w110w011w112w013w114w115w321w423w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x733c7779…a647
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xee6105c1…e980
0x34b655…2a6f
6 touches
3 conflicts
0x36126dcb…ca1e
0x34b655…2a6f
4 touches
1 conflict
0x4f858307…7642
0x34b655…2a6f
4 touches
1 conflict
0x6d15aba9…eb7b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity