← previous blocknext block →recent activity
Analyzing
Block #108,376,971
15 transactions · 13 stateful · 2026-09-27 05:04:02 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,376,971 · 15 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
2w03w19w010w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a456c98…6916
0x34b655…2a6f
4 touches
1 conflict
0x87b3c188…6ea2
0x34b655…2a6f
4 touches
1 conflict
0x3b8da5cc…e045
0x34b655…2a6f
4 touches
1 conflict
0xa152fb05…fc83
0x34b655…2a6f
4 touches
1 conflict
0xe965c5b3…8674
0x34b655…2a6f
4 touches
1 conflict
0xfe19fcfe…23be
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
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 0x6a456c98e1…fd6916
Audit this contract →
← previous block·next block →recent activity