← previous blocknext block →recent activity
Analyzing
Block #93,473,742
16 transactions · 16 stateful · 2026-08-05 23:05:35 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,473,742 · 16 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
2w03w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xb1b58b33…874f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12d8dc13…85bb
0x34b655…2a6f
2 touches
0 conflicts
0x528d384f…663d
0x34b655…2a6f
2 touches
0 conflicts
0x5c68f52e…31ee
0x34b655…2a6f
2 touches
0 conflicts
0x8191bcf8…ef46
0x34b655…2a6f
2 touches
0 conflicts
0xc8b7d55e…1afd
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity