← previous blocknext block →recent activity
Analyzing
Block #108,363,405
11 transactions · 11 stateful · 2026-09-27 03:55:47 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,363,405 · 11 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
3w04w15w26w39w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0x1ad8153e…06bf
0x34b655…2a6f
4 touches
1 conflict
0x31f70b07…2200
0x34b655…2a6f
4 touches
1 conflict
0x37f93b32…cc57
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x63748984…1fb3
0x34b655…2a6f
4 touches
1 conflict
0x68bb45cc…10d8
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 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity