← previous blocknext block →recent activity
Analyzing
Block #81,013,925
14 transactions · 7 stateful · 2026-06-13 12:48:53 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,013,925 · 14 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
1w02w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x02d895f0…2b93
0x34b655…2a6f
4 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
2 touches
0 conflicts
0x02a19e34…c782
0x34b655…2a6f
2 touches
0 conflicts
0x0487d7b3…f375
0x34b655…2a6f
2 touches
0 conflicts
0x06df379f…2653
0x34b655…2a6f
2 touches
0 conflicts
0x3e505a15…70f8
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity