← previous blocknext block →recent activity
Analyzing
Block #84,314,723
18 transactions · 12 stateful · 2026-06-28 19:50:29 UTC
Parallelism
89/100
Blocked
8%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,314,723 · 18 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
5w016w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d4b0baf…1423
0x34b655…2a6f
4 touches
1 conflict
0x5a5dd7b4…fba4
0x34b655…2a6f
4 touches
1 conflict
0x99c320a0…b4a8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf0b63b44…0c3d
0x34b655…2a6f
4 touches
1 conflict
0xfd4e2262…cd8c
0x34b655…2a6f
4 touches
1 conflict
0x77bc2523…0907
0x065c9d…c394
2 touches
0 conflicts
0xcdb8b85a…589f
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 0x1d4b0bafd5…641423
Audit this contract →
← previous block·next block →recent activity