← previous blocknext block →recent activity
Analyzing
Block #105,921,898
37 transactions · 28 stateful · 2026-09-18 15:03:48 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,921,898 · 37 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w28w39w410w512w021w625w527w128w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x3018a378…d7bb
0x34b655…2a6f
10 touches
10 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0x3a429191…9cda
0x34b655…2a6f
8 touches
6 conflicts
0xdb11940a…519b
0x34b655…2a6f
7 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x1379aed4…8fb8
0x34b655…2a6f
6 touches
3 conflicts
0x34455398…05b9
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity