← previous blocknext block →recent activity
Analyzing
Block #108,605,007
25 transactions · 18 stateful · 2026-09-28 00:12:04 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,605,007 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w09w112w214w116w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea57afd0…4232
0x34b655…2a6f
6 touches
3 conflicts
0xe2c4da1c…0e42
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x5922c26d…3312
0x851145…3f07
4 touches
1 conflict
0xe47f0750…4816
0x851145…3f07
4 touches
1 conflict
0x78e7f7af…0e0f
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
3 conflicts on slot 0xea57afd097…7f4232
Audit this contract →
← previous block·next block →recent activity