← previous blocknext block →recent activity
Analyzing
Block #83,665,506
17 transactions · 16 stateful · 2026-06-25 19:43:15 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,665,506 · 17 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
2w03w16w012w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c48b3ac…a03c
0x34b655…2a6f
4 touches
1 conflict
0x8175ff23…d3a1
0x34b655…2a6f
4 touches
1 conflict
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0x0ec126c8…5104
0x34b655…2a6f
4 touches
1 conflict
0x16d0d759…b204
0x34b655…2a6f
2 touches
0 conflicts
0x221215c6…84b4
0x34b655…2a6f
2 touches
0 conflicts
0x37a276a3…673f
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 0x1c48b3acf3…40a03c
Audit this contract →
← previous block·next block →recent activity