← previous blocknext block →recent activity
Analyzing
Block #108,360,806
21 transactions · 18 stateful · 2026-09-27 03:42:42 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,360,806 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w19w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
4 touches
1 conflict
0xa93fef74…94b3
0x37db7f…ec7b
4 touches
1 conflict
0xdbcc4ab8…2aba
0x37db7f…ec7b
4 touches
1 conflict
0xe3e67fe3…e754
0x37db7f…ec7b
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x199a4f01…2183
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
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
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity