← previous blocknext block →recent activity
Analyzing
Block #108,796,798
38 transactions · 26 stateful · 2026-09-28 16:18:08 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
1.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,796,798 · 38 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w29w310w411w512w616w723w124w226w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724ba0cf…01c7
0x34b655…2a6f
16 touches
28 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
14 touches
21 conflicts
0x0d54fa3e…3b3c
0x34b655…2a6f
14 touches
21 conflicts
0x3b437bbf…4c51
0x34b655…2a6f
14 touches
21 conflicts
0x68a6938f…55c8
0x34b655…2a6f
14 touches
21 conflicts
0x739123da…57f3
0x34b655…2a6f
14 touches
21 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 0x724ba0cf22…b301c7
Audit this contract →
← previous block·next block →recent activity