← previous blocknext block →recent activity
Analyzing
Block #108,524,190
15 transactions · 14 stateful · 2026-09-27 17:25:04 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,524,190 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9674d680…261b
0x34b655…2a6f
4 touches
1 conflict
0xa1c580ae…578a
0x34b655…2a6f
4 touches
1 conflict
0xb64252f2…a7c3
0x34b655…2a6f
4 touches
1 conflict
0xbe9a3422…22ec
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd33a3d56…2ae3
0x34b655…2a6f
4 touches
1 conflict
0xf8b7e65f…2816
0x34b655…2a6f
4 touches
1 conflict
0x4292a836…9ed5
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
1 conflict on slot 0x9674d68053…c5261b
Audit this contract →
← previous block·next block →recent activity