← previous blocknext block →recent activity
Analyzing
Block #84,348,010
32 transactions · 26 stateful · 2026-06-28 23:32:18 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,348,010 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w211w012w113w014w116w017w220w021w122w225w028w129w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23ab8481…52d5
0x34b655…2a6f
6 touches
3 conflicts
0x2a897c31…0313
0x34b655…2a6f
6 touches
3 conflicts
0x08aa8a0d…fc37
0x065c9d…c394
5 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x6a53b1c0…c3f2
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x8ad7ff3b…5264
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x23ab8481d2…ea52d5
Audit this contract →
← previous block·next block →recent activity