← previous blocknext block →recent activity
Analyzing
Block #93,372,113
16 transactions · 15 stateful · 2026-08-05 14:34:38 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,372,113 · 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
4w07w08w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fd12b6c…02cc
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0xe8272cde…df12
0x34b655…2a6f
4 touches
1 conflict
0xe8272cde…df13
0x34b655…2a6f
4 touches
1 conflict
0x6456a99e…d49d
0x34b655…2a6f
3 touches
1 conflict
0xf23913fb…4366
0x34b655…2a6f
3 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0x9ff176a9…152e
0x065c9d…c394
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 0x2fd12b6c73…8702cc
Audit this contract →
← previous block·next block →recent activity