← previous blocknext block →recent activity
Analyzing
Block #108,873,402
22 transactions · 22 stateful · 2026-09-28 22:46:14 UTC
Parallelism
91/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,873,402 · 22 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
5w08w115w017w118w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4de06ee…61f3
0x34b655…2a6f
4 touches
1 conflict
0x41f69129…1c71
0x34b655…2a6f
4 touches
1 conflict
0x4ae3b148…7ed2
0x34b655…2a6f
4 touches
1 conflict
0x5e6138c7…9a5e
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x06ce5d4b…c122
0x34ae4d…3fc5
2 touches
0 conflicts
0x2f74f175…9286
0x34ae4d…3fc5
2 touches
0 conflicts
0x2f74f175…9287
0x34ae4d…3fc5
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 0xe4de06ee1f…e161f3
Audit this contract →
← previous block·next block →recent activity