← previous blocknext block →recent activity
Analyzing
Block #83,483,885
7 transactions · 6 stateful · 2026-06-24 23:31:27 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,483,885 · 7 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x8406e802…327c
0x34b655…2a6f
4 touches
1 conflict
0xd1a8b9bd…6f8c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe20a9313…c20a
0x34b655…2a6f
4 touches
1 conflict
0x0f3b22bf…e574
0x34b655…2a6f
2 touches
0 conflicts
0x112c35bc…2afc
0x34b655…2a6f
2 touches
0 conflicts
0x200db05e…6327
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 0x03fb27fddd…f00c06
Audit this contract →
← previous block·next block →recent activity