← previous blocknext block →recent activity
Analyzing
Block #106,944,853
19 transactions · 17 stateful · 2026-09-22 04:53:30 UTC
Parallelism
63/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,944,853 · 19 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
1w02w04w06w17w212w113w314w415w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26799298…9ff2
0x34b655…2a6f
12 touches
15 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
8 touches
6 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
8 touches
6 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 conflicts
0x858e40c0…7e30
0x34b655…2a6f
6 touches
3 conflicts
0xa4b19ffb…1dee
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 0x2679929847…049ff2
Audit this contract →
← previous block·next block →recent activity