← previous blocknext block →recent activity
Analyzing
Block #108,566,147
23 transactions · 21 stateful · 2026-09-27 20:56:28 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,566,147 · 23 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
1w05w06w18w010w112w013w114w115w216w217w318w422w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x7462b8f2…6312
0x34b655…2a6f
6 touches
3 conflicts
0x1f84ce8a…5acc
0x34b655…2a6f
4 touches
1 conflict
0x2e84bea1…20bc
0x34b655…2a6f
4 touches
1 conflict
0xed8224d3…528e
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x132b9de1…183b
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity