← previous blocknext block →recent activity
Analyzing
Block #108,113,659
39 transactions · 30 stateful · 2026-09-26 06:58:54 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
1.03
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,113,659 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w28w310w011w114w417w224w331w533w135w436w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74e485b1…d380
0x34b655…2a6f
12 touches
15 conflicts
0x5f77d607…2c84
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 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
15 conflicts on slot 0x74e485b13a…f0d380
Audit this contract →
← previous block·next block →recent activity