← previous blocknext block →recent activity
Analyzing
Block #108,658,323
19 transactions · 18 stateful · 2026-09-28 04:40:36 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,658,323 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w18w010w112w216w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x794e4a11…3f4f
0x34b655…2a6f
6 touches
3 conflicts
0xdaee24f5…2f77
0xd32edf…ff58
5 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x4aa8b305…4ace
0xcc9410…4c10
4 touches
1 conflict
0x7a12283f…b18a
0x34ae4d…3fc5
2 touches
0 conflicts
0x915c095e…c1e5
0x34ae4d…3fc5
2 touches
0 conflicts
0xcfe06a18…b5b5
0x34ae4d…3fc5
2 touches
0 conflicts
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 0x794e4a1127…a63f4f
Audit this contract →
← previous block·next block →recent activity