← previous blocknext block →recent activity
Analyzing
Block #105,618,220
25 transactions · 24 stateful · 2026-09-17 13:33:03 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,618,220 · 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
2w03w14w26w07w111w012w015w118w019w320w223w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03626e21…e8e4
0x34b655…2a6f
6 touches
3 conflicts
0x15ae3bf3…2507
0x34b655…2a6f
6 touches
3 conflicts
0xfc2493d3…6898
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x232df012…c608
0x34b655…2a6f
6 touches
3 conflicts
0x42daad7f…630b
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
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 0x03626e2108…d1e8e4
Audit this contract →
← previous block·next block →recent activity