← previous blocknext block →recent activity
Analyzing
Block #108,531,783
20 transactions · 18 stateful · 2026-09-27 18:03:16 UTC
Parallelism
90/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,531,783 · 20 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
1w02w13w05w17w08w19w010w113w014w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f4bea26…d3c6
0x34b655…2a6f
4 touches
1 conflict
0x59f14360…45d6
0x34b655…2a6f
4 touches
1 conflict
0x866110ca…7080
0x34b655…2a6f
4 touches
1 conflict
0xa57f5ee8…9220
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xefc465f2…88c5
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x451e482b…7e7d
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 0x1f4bea26e3…41d3c6
Audit this contract →
← previous block·next block →recent activity