← previous blocknext block →recent activity
Analyzing
Block #106,185,685
19 transactions · 17 stateful · 2026-09-19 13:11:32 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,185,685 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w08w19w112w013w214w316w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x125cf0f0…08e2
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xee8c7481…8fd0
0x34b655…2a6f
4 touches
1 conflict
0xf90c6521…d8f0
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
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 0x125cf0f067…8508e2
Audit this contract →
← previous block·next block →recent activity