← previous blocknext block →recent activity
Analyzing
Block #84,241,942
11 transactions · 10 stateful · 2026-06-28 11:45:42 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,241,942 · 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
1w02w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff4a358a…762f
0x34b655…2a6f
4 touches
1 conflict
0x0ae85bb4…7370
0x34b655…2a6f
4 touches
1 conflict
0x17cc5ec3…ae0e
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa5c492cb…4b45
0xd32edf…ff58
3 touches
1 conflict
0x9492718a…0262
0x40c49f…2af0
2 touches
0 conflicts
0xaae9bba8…46ca
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 0xff4a358a00…50762f
Audit this contract →
← previous block·next block →recent activity