← previous blocknext block →recent activity
Analyzing
Block #96,279,010
13 transactions · 13 stateful · 2026-08-15 18:48:08 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,279,010 · 13 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
1w02w13w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49ffd065…33d1
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x03c38bff…f48f
0x34b655…2a6f
2 touches
0 conflicts
0x058570f0…7e36
0x34b655…2a6f
2 touches
0 conflicts
0x1294a92c…f91e
0x34b655…2a6f
2 touches
0 conflicts
0x14eb2f47…8a2e
0x34b655…2a6f
2 touches
0 conflicts
0x1b49f420…7fe1
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 0x49ffd065b3…cd33d1
Audit this contract →
← previous block·next block →recent activity