← previous blocknext block →recent activity
Analyzing
Block #93,452,100
12 transactions · 12 stateful · 2026-08-05 21:16:47 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,452,100 · 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
2w05w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc351d6d…256b
0x34b655…2a6f
4 touches
1 conflict
0x98212952…9ba6
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0515ff15…c530
0x34b655…2a6f
2 touches
0 conflicts
0x12d8dc13…85bb
0x34b655…2a6f
2 touches
0 conflicts
0x1404b00b…d8b3
0x34b655…2a6f
2 touches
0 conflicts
0x1c11fd01…6239
0x34b655…2a6f
2 touches
0 conflicts
0x3b689fd2…629c
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 0xcc351d6dd2…b1256b
Audit this contract →
← previous block·next block →recent activity