← previous blocknext block →recent activity
Analyzing
Block #93,490,034
12 transactions · 12 stateful · 2026-08-06 00:27:29 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,490,034 · 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
2w03w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64f1eb47…cd27
0x34b655…2a6f
4 touches
1 conflict
0x88413c1a…7783
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0x10797f0b…439a
0x34b655…2a6f
2 touches
0 conflicts
0x24b6091e…d294
0x34b655…2a6f
2 touches
0 conflicts
0x27d09143…3daf
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 0x64f1eb4791…95cd27
Audit this contract →
← previous block·next block →recent activity