← previous blocknext block →recent activity
Analyzing
Block #83,195,475
15 transactions · 12 stateful · 2026-06-23 15:24:53 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,195,475 · 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
6w09w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x4ee5a465…4ca2
0x34b655…2a6f
3 touches
1 conflict
0x0953719e…c3e2
0x065c9d…c394
2 touches
0 conflicts
0x1019d317…d54a
0x065c9d…c394
2 touches
0 conflicts
0x96539d74…4915
0x065c9d…c394
2 touches
0 conflicts
0xb1e9c798…cbdf
0x065c9d…c394
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 0x8e5cc69035…0db06b
Audit this contract →
← previous block·next block →recent activity