← previous blocknext block →recent activity
Analyzing
Block #95,201,247
20 transactions · 19 stateful · 2026-08-12 00:12:04 UTC
Parallelism
75/100
Blocked
26%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,201,247 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w110w011w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cc5ca07…1022
0xe52b14…7230
10 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0xd42c0a7f…ecdf
0xe52b14…7230
10 touches
10 conflicts
0xd42c0a7f…ece1
0xe52b14…7230
10 touches
10 conflicts
0x6cc5ca07…1020
0xe52b14…7230
10 touches
10 conflicts
0x4cd398fd…5409
0xe52b14…7230
8 touches
10 conflicts
0x1dd9b416…50be
0xe52b14…7230
7 touches
6 conflicts
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
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: 0xe52b1424…bb7230
10 conflicts on slot 0x6cc5ca0712…1f1022
Audit this contract →
← previous block·next block →recent activity