← previous blocknext block →recent activity
Analyzing
Block #106,916,549
25 transactions · 20 stateful · 2026-09-22 02:31:02 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,916,549 · 25 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
1w03w15w18w112w013w114w215w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53ca1284…cb2c
0x34b655…2a6f
16 touches
28 conflicts
0xf782ee27…41cd
0x34b655…2a6f
16 touches
28 conflicts
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
2 touches
0 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 0x53ca128412…cacb2c
Audit this contract →
← previous block·next block →recent activity