← previous blocknext block →recent activity
Analyzing
Block #105,402,645
19 transactions · 16 stateful · 2026-09-16 19:28:04 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,402,645 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w16w07w08w114w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x08d53462…97ef
0x34ae4d…3fc5
4 touches
1 conflict
0x5a409e7f…09b6
0x34ae4d…3fc5
4 touches
1 conflict
0x62811193…1867
0x34ae4d…3fc5
4 touches
1 conflict
0x62811193…1868
0x34ae4d…3fc5
4 touches
1 conflict
0x6cd67eff…f738
0x34ae4d…3fc5
4 touches
1 conflict
0x7a12283f…b18a
0x34ae4d…3fc5
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity