← previous blocknext block →recent activity
Analyzing
Block #105,848,415
25 transactions · 25 stateful · 2026-09-18 08:53:05 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
2.12
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,848,415 · 25 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
1w02w13w24w35w38w49w010w011w112w213w314w415w520w323w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x6c6f37ba…c20c
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity