← previous blocknext block →recent activity
Analyzing
Block #105,402,494
30 transactions · 29 stateful · 2026-09-16 19:27:19 UTC
Parallelism
60/100
Blocked
52%
Avg conflicts / tx
1.33
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #105,402,494 · 30 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w08w09w510w617w723w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93aff45d…1722
0x34b655…2a6f
14 touches
21 conflicts
0xa5f8777f…9458
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
10 touches
10 conflicts
0xe1cc9521…a148
0x34b655…2a6f
6 touches
3 conflicts
0xed252c0a…b47e
0x34b655…2a6f
4 touches
1 conflict
0xf11eb80a…925b
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
21 conflicts on slot 0x93aff45da2…d81722
Audit this contract →
← previous block·next block →recent activity