← previous blocknext block →recent activity
Analyzing
Block #108,377,421
16 transactions · 16 stateful · 2026-09-27 05:06:18 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,377,421 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w010w111w112w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc30f476d…479a
0x34b655…2a6f
4 touches
1 conflict
0xe965c5b3…8674
0x34b655…2a6f
4 touches
1 conflict
0xed8224d3…528e
0x34b655…2a6f
4 touches
1 conflict
0xfe19fcfe…23be
0x34b655…2a6f
4 touches
1 conflict
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x097cee83…0878
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
1 conflict on slot 0xc30f476d3a…bb479a
Audit this contract →
← previous block·next block →recent activity