← previous blocknext block →recent activity
Analyzing
Block #102,173,626
15 transactions · 13 stateful · 2026-09-05 11:32:04 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,173,626 · 15 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
2w03w19w010w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b689fd2…629c
0x34b655…2a6f
4 touches
1 conflict
0x41c56387…a8f6
0x34b655…2a6f
4 touches
1 conflict
0x4ae38164…15f0
0x34b655…2a6f
4 touches
1 conflict
0x545d33cf…b72c
0x34b655…2a6f
4 touches
1 conflict
0x62b13313…bbe8
0x34b655…2a6f
4 touches
1 conflict
0x6d105005…3cc9
0x34b655…2a6f
4 touches
1 conflict
0x6d5af916…7e39
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
1 conflict on slot 0x3b689fd2ea…3f629c
Audit this contract →
← previous block·next block →recent activity