← previous blocknext block →recent activity
Analyzing
Block #106,921,724
28 transactions · 18 stateful · 2026-09-22 02:57:05 UTC
Parallelism
89/100
Blocked
22%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,921,724 · 28 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w116w017w122w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63b90da2…4b0c
0x34b655…2a6f
6 touches
3 conflicts
0xb57ead8a…c75d
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
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
3 conflicts on slot 0x63b90da234…864b0c
Audit this contract →
← previous block·next block →recent activity