← previous blocknext block →recent activity
Analyzing
Block #84,186,811
15 transactions · 13 stateful · 2026-06-28 05:38:11 UTC
Parallelism
87/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,186,811 · 15 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
2w04w05w17w19w010w112w013w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99ebc4d…22f9
0x34b655…2a6f
4 touches
1 conflict
0xdfc5f346…7b42
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
1 conflict on slot 0xe99ebc4d01…5b22f9
Audit this contract →
← previous block·next block →recent activity