← previous blocknext block →recent activity
Analyzing
Block #93,498,538
13 transactions · 12 stateful · 2026-08-06 01:10:14 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,498,538 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w38w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2b37cdc…e470
0x34b655…2a6f
4 touches
1 conflict
0xd676e291…3ecf
0x34b655…2a6f
4 touches
1 conflict
0x41469894…5990
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x33366bcb…32b0
0x34b655…2a6f
4 touches
1 conflict
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
2 touches
0 conflicts
0x1f520edb…23d1
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 0xc2b37cdc32…c4e470
Audit this contract →
← previous block·next block →recent activity