← previous blocknext block →recent activity
Analyzing
Block #96,143,399
12 transactions · 12 stateful · 2026-08-15 07:26:04 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,143,399 · 12 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
2w03w14w16w08w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6939e474…4256
0x34b655…2a6f
4 touches
1 conflict
0x3a5cd691…1b32
0x968279…9342
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x0b88be78…0600
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xc7d08bca…e210
0x34b655…2a6f
4 touches
1 conflict
0x3d118aca…1a2e
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: Perpl
1 conflict on slot 0x6939e474b1…154256
Audit this contract →
← previous block·next block →recent activity