← previous blocknext block →recent activity
Analyzing
Block #106,041,352
30 transactions · 27 stateful · 2026-09-19 01:05:10 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.73
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,041,352 · 30 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
1w02w03w111w112w014w117w018w119w220w221w323w424w527w528w629w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb041f2a8…a44a
0x34b655…2a6f
6 touches
3 conflicts
0xb36c74c3…2567
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0xe2c4da1c…0e41
0x34b655…2a6f
6 touches
3 conflicts
0xe174ab5b…3f03
0x34b655…2a6f
5 touches
3 conflicts
0x9feec606…4ad5
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity