← previous blocknext block →recent activity
Analyzing
Block #83,623,798
13 transactions · 11 stateful · 2026-06-25 15:04:55 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,623,798 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x758bd24b…cc0c
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0x51fde237…36d5
0x34b655…2a6f
2 touches
0 conflicts
0x60146498…2704
0x34b655…2a6f
2 touches
0 conflicts
0x617629c3…3907
0x34b655…2a6f
2 touches
0 conflicts
0x6767aeb1…eabc
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 0x758bd24bd8…71cc0c
Audit this contract →
← previous block·next block →recent activity