← previous blocknext block →recent activity
Analyzing
Block #102,413,242
25 transactions · 23 stateful · 2026-09-06 07:46:05 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,413,242 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w114w015w116w218w320w021w122w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xafe81a7b…bcbf
0x34b655…2a6f
6 touches
3 conflicts
0xcc40466c…8149
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6bab0076…422b
0x34b655…2a6f
4 touches
1 conflict
0x766a8dae…0862
0x34b655…2a6f
4 touches
1 conflict
0x9a1cdfbe…3b93
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity