← previous blocknext block →recent activity
Analyzing
Block #84,348,616
19 transactions · 17 stateful · 2026-06-28 23:36:20 UTC
Parallelism
89/100
Blocked
6%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,348,616 · 19 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
5w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x179fd795…fbe5
0x34b655…2a6f
4 touches
1 conflict
0x6c0f2706…02c5
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x196a5752…b49c
0x065c9d…c394
2 touches
0 conflicts
0x501f707c…f82a
0x065c9d…c394
2 touches
0 conflicts
0x511899bc…4346
0x065c9d…c394
2 touches
0 conflicts
0xa59139a8…1289
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 0x179fd795e3…75fbe5
Audit this contract →
← previous block·next block →recent activity