← previous blocknext block →recent activity
Analyzing
Block #83,847,714
15 transactions · 12 stateful · 2026-06-26 15:59:04 UTC
Parallelism
73/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,847,714 · 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
5w012w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6c88e49…7bbf
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf4f4af3b…c5bd
0x34b655…2a6f
4 touches
1 conflict
0x3710478b…a791
0x34b655…2a6f
4 touches
1 conflict
0x58f7f297…bdd8
0x34b655…2a6f
4 touches
1 conflict
0x7e17e82a…9748
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
0x9dbefc67…4855
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
3 conflicts on slot 0xb6c88e4974…7d7bbf
Audit this contract →
← previous block·next block →recent activity