← previous blocknext block →recent activity
Analyzing
Block #83,843,317
15 transactions · 12 stateful · 2026-06-26 15:29:45 UTC
Parallelism
87/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,843,317 · 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
7w011w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13e6be9d…4b8b
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0xc47ca59a…b171
0x34b655…2a6f
4 touches
1 conflict
0x250efed1…5a09
0x068f22…7908
2 touches
0 conflicts
0xaa5d1ec6…e2af
0x068f22…7908
2 touches
0 conflicts
0x741048ab…1e62
0x09475a…400f
2 touches
0 conflicts
0xee2e48fa…c427
0x09475a…400f
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0x13e6be9db1…724b8b
Audit this contract →
← previous block·next block →recent activity