← previous blocknext block →recent activity
Analyzing
Block #84,429,648
11 transactions · 10 stateful · 2026-06-29 08:36:29 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,429,648 · 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
6w07w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf195ad96…e0c3
0x34b655…2a6f
4 touches
1 conflict
0x130b8bf2…8fd7
0x34b655…2a6f
4 touches
1 conflict
0x9968da10…0ab5
0x34b655…2a6f
4 touches
1 conflict
0x9ad4d28a…c788
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0xe75b1435…38f4
0x57ea24…2cec
2 touches
0 conflicts
0xf5c7a70d…e703
0x690ad2…09d3
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 0xf195ad96b6…00e0c3
Audit this contract →
← previous block·next block →recent activity