← previous blocknext block →recent activity
Analyzing
Block #108,653,798
29 transactions · 26 stateful · 2026-09-28 04:17:48 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,653,798 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w09w111w212w314w015w119w220w321w323w424w425w027w128w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51f2c25d…7bf1
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x43e3decb…be40
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x5d416e45…e426
0x34b655…2a6f
4 touches
1 conflict
0x68f7aaba…88df
0x34b655…2a6f
4 touches
1 conflict
0x724ba0cf…01c7
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
6 conflicts on slot 0x51f2c25d57…7d7bf1
Audit this contract →
← previous block·next block →recent activity