← previous blocknext block →recent activity
Analyzing
Block #105,922,392
19 transactions · 18 stateful · 2026-09-18 15:06:17 UTC
Parallelism
84/100
Blocked
44%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,922,392 · 19 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
1w02w03w15w06w17w212w113w216w217w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5f71148…62ee
0x40c49f…2af0
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x3439deb5…2fa4
0x40c49f…2af0
6 touches
3 conflicts
0xc6615a36…3cf0
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe07ad0d2…3af9
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: 0x40c49f17…d22af0
3 conflicts on slot 0xa5f7114836…0662ee
Audit this contract →
← previous block·next block →recent activity