← previous blocknext block →recent activity
Analyzing
Block #93,761,614
17 transactions · 14 stateful · 2026-08-06 23:12:45 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,761,614 · 17 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
1w03w110w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb8746edd…bc38
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x85d5cb6a…3a90
0x34b655…2a6f
4 touches
1 conflict
0x23f0daac…3360
0x065c9d…c394
2 touches
0 conflicts
0x9190da0c…0657
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
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 0xb8746edd05…cebc38
Audit this contract →
← previous block·next block →recent activity