← previous blocknext block →recent activity
Analyzing
Block #95,530,891
16 transactions · 14 stateful · 2026-08-13 04:03:43 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,530,891 · 16 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
1w02w17w010w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa124184b…1dcb
0x34b655…2a6f
4 touches
1 conflict
0x24521815…c677
0x34b655…2a6f
4 touches
1 conflict
0x508bbf1b…fe95
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0x0bf2e71c…3846
0x34b655…2a6f
2 touches
0 conflicts
0x1c255c26…11dd
0x34b655…2a6f
2 touches
0 conflicts
0x203f132b…89fc
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 0xa124184b0e…fc1dcb
Audit this contract →
← previous block·next block →recent activity