← previous blocknext block →recent activity
Analyzing
Block #105,749,415
17 transactions · 15 stateful · 2026-09-18 00:33:24 UTC
Parallelism
59/100
Blocked
73%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,749,415 · 17 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
1w02w13w25w28w39w410w311w412w513w615w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5847c4d…a65c
0x34b655…2a6f
10 touches
10 conflicts
0x73c6bbd3…9969
0x34b655…2a6f
10 touches
10 conflicts
0x61bf2d7f…38f1
0x34b655…2a6f
8 touches
6 conflicts
0xba5743c7…21c4
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
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
10 conflicts on slot 0xc5847c4d32…49a65c
Audit this contract →
← previous block·next block →recent activity