← previous blocknext block →recent activity
Analyzing
Block #106,241,964
19 transactions · 18 stateful · 2026-09-19 17:54:53 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,241,964 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w06w17w18w110w211w113w114w215w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f1c2eba…7281
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0a9fcba0…98af
0x34b655…2a6f
4 touches
1 conflict
0x10499d94…6a8d
0x34b655…2a6f
4 touches
1 conflict
0x65e57979…e43d
0x34b655…2a6f
4 touches
1 conflict
0x708d7a74…09e3
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x8f1c2eba57…717281
Audit this contract →
← previous block·next block →recent activity