← previous blocknext block →recent activity
Analyzing
Block #105,617,887
37 transactions · 36 stateful · 2026-09-17 13:31:22 UTC
Parallelism
60/100
Blocked
61%
Avg conflicts / tx
2.27
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #105,617,887 · 37 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w18w19w210w311w412w513w614w715w819w122w823w826w232w1035w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0x6b68679f…a232
0x34b655…2a6f
10 touches
10 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
10 touches
10 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
8 touches
6 conflicts
0x75f36d60…8556
0x34b655…2a6f
8 touches
6 conflicts
0x8b7e5c4e…5fae
0x34b655…2a6f
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
36 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity