← previous blocknext block →recent activity
Analyzing
Block #108,619,331
23 transactions · 22 stateful · 2026-09-28 01:24:13 UTC
Parallelism
70/100
Blocked
45%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,619,331 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w07w110w211w312w013w416w521w122w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b60b708…5b4b
0x34ae4d…3fc5
8 touches
6 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
8 touches
6 conflicts
0x06e40499…165e
0x34ae4d…3fc5
8 touches
6 conflicts
0xf3d7a307…4d63
0x065c9d…c394
8 touches
6 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
6 touches
3 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: 0x34ae4d08…a73fc5
6 conflicts on slot 0x1b60b70879…2f5b4b
Audit this contract →
← previous block·next block →recent activity