← previous blocknext block →recent activity
Analyzing
Block #108,278,654
19 transactions · 18 stateful · 2026-09-26 20:49:17 UTC
Parallelism
63/100
Blocked
39%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,278,654 · 19 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
1w06w17w28w39w410w512w615w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x17c3727d…cb0e
0x34b655…2a6f
4 touches
1 conflict
0x214d5ae7…8f21
0x34b655…2a6f
4 touches
1 conflict
0x283c8b4f…4f4a
0x34b655…2a6f
4 touches
1 conflict
0x49956f11…1283
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x90affd2f…be9f
0x34b655…2a6f
4 touches
1 conflict
0x97620bb8…d40a
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity