← previous blocknext block →recent activity
Analyzing
Block #84,619,337
11 transactions · 9 stateful · 2026-06-30 05:41:41 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,619,337 · 11 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
1w02w13w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x159b8597…48a4
0x34b655…2a6f
4 touches
1 conflict
0xb44d5376…33cc
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x40b5f387…a164
0x34b655…2a6f
3 touches
1 conflict
0x10199031…6659
0x40c49f…2af0
2 touches
0 conflicts
0x448a363c…a731
0x40c49f…2af0
2 touches
0 conflicts
0x6e14ab40…e8a6
0x40c49f…2af0
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 0x159b8597f3…8f48a4
Audit this contract →
← previous block·next block →recent activity