← previous blocknext block →recent activity
Analyzing
Block #105,841,702
61 transactions · 58 stateful · 2026-09-18 08:19:11 UTC
Parallelism
74/100
Blocked
64%
Avg conflicts / tx
2.75
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #105,841,702 · 61 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w17w08w110w113w014w115w217w018w120w229w230w131w332w233w334w335w436w554w155w257w458w559w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7dba3206…9c03
0x34b655…2a6f
22 touches
55 conflicts
0x5684aadd…8d62
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x8ae87135…d426
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
10 touches
10 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
55 conflicts on slot 0x7dba3206bc…6e9c03
Audit this contract →
← previous block·next block →recent activity