← previous blocknext block →recent activity
Analyzing
Block #108,654,649
38 transactions · 31 stateful · 2026-09-28 04:22:05 UTC
Parallelism
87/100
Blocked
39%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,654,649 · 38 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
2w03w15w06w07w18w09w117w018w219w321w024w425w026w027w128w234w135w236w337w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ef6135c…f384
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0xbefdde57…cd0e
0x34b655…2a6f
4 touches
1 conflict
0xc8f8f6c0…0e69
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 0x0ef6135c4d…b4f384
Audit this contract →
← previous block·next block →recent activity