← previous blocknext block →recent activity
Analyzing
Block #108,503,522
24 transactions · 24 stateful · 2026-09-27 15:41:02 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.88
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,503,522 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w113w014w015w116w217w318w419w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xdc7b9eda…e616
0x34b655…2a6f
8 touches
6 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
8 touches
6 conflicts
0x368baece…4048
0x34b655…2a6f
6 touches
3 conflicts
0x5900e8aa…2391
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x94435298…2c33
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
10 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity