← previous blocknext block →recent activity
Analyzing
Block #84,136,246
11 transactions · 7 stateful · 2026-06-28 00:01:46 UTC
Parallelism
82/100
Blocked
14%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,136,246 · 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
8w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c1bf011…6921
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x19ce481d…6c36
0x34b655…2a6f
2 touches
0 conflicts
0x23eaa37b…6efc
0x34b655…2a6f
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 0x6c1bf011fc…376921
Audit this contract →
← previous block·next block →recent activity