← previous blocknext block →recent activity
Analyzing
Block #83,902,169
15 transactions · 10 stateful · 2026-06-26 22:02:22 UTC
Parallelism
87/100
Blocked
10%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,902,169 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0xe02484a6…c32e
0xc8689a…ee79
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x12dd43c9…22d9
0x34b655…2a6f
2 touches
0 conflicts
0x4bd72ffb…090e
0x34b655…2a6f
2 touches
0 conflicts
0x94e7f277…471b
0x34b655…2a6f
2 touches
0 conflicts
0xce61a4da…c844
0x34b655…2a6f
2 touches
0 conflicts
0xf8fd1cbd…d093
0x34b655…2a6f
2 touches
0 conflicts
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 0x6f6fc26c68…133e34
Audit this contract →
← previous block·next block →recent activity