← previous blocknext block →recent activity
Analyzing
Block #108,603,361
13 transactions · 13 stateful · 2026-09-28 00:03:47 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,603,361 · 13 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
2w03w17w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0a62e96…028d
0x34b655…2a6f
4 touches
1 conflict
0xe7e6031b…b25d
0x34b655…2a6f
4 touches
1 conflict
0xefc465f2…88c5
0x34b655…2a6f
4 touches
1 conflict
0xf3767a05…dc07
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x1abfd3ae…2999
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 0xe0a62e9693…78028d
Audit this contract →
← previous block·next block →recent activity