← previous blocknext block →recent activity
Analyzing
Block #93,579,426
9 transactions · 9 stateful · 2026-08-06 07:56:51 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,579,426 · 9 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x378c030c…a8a5
0x34b655…2a6f
4 touches
1 conflict
0x90c0594a…5f65
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x378c030c…a8a4
0x34b655…2a6f
4 touches
1 conflict
0xb6b74ae0…8d5e
0xea1b8e…c5ec
2 touches
0 conflicts
0xd8eb2d31…2ac0
0xea1b8e…c5ec
2 touches
0 conflicts
0xdad4a443…9158
0xea1b8e…c5ec
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 0x378c030cda…2ba8a5
Audit this contract →
← previous block·next block →recent activity