← previous blocknext block →recent activity
Analyzing
Block #105,845,180
19 transactions · 18 stateful · 2026-09-18 08:36:47 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,845,180 · 19 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
2w07w19w210w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18195fec…2bb3
0x34b655…2a6f
16 touches
28 conflicts
0xfd7f5b55…4994
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
10 touches
10 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0x89999c15…fdac
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x427aa12f…e796
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
28 conflicts on slot 0x18195fec6e…992bb3
Audit this contract →
← previous block·next block →recent activity