← previous blocknext block →recent activity
Analyzing
Block #108,310,232
19 transactions · 16 stateful · 2026-09-26 23:28:12 UTC
Parallelism
74/100
Blocked
31%
Avg conflicts / tx
0.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,310,232 · 19 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
4w07w012w113w214w315w117w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x8217591f…c1b9
0x34b655…2a6f
4 touches
1 conflict
0xc4646dd5…0b8e
0x34b655…2a6f
4 touches
1 conflict
0xe965c5b3…8674
0x34b655…2a6f
4 touches
1 conflict
0xfaa57f54…8aeb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa3ff1ab2…8ae3
0x34b655…2a6f
2 touches
0 conflicts
0xfadc118d…5d64
0x34b655…2a6f
2 touches
0 conflicts
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
3 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity