← previous blocknext block →recent activity
Analyzing
Block #93,670,384
21 transactions · 21 stateful · 2026-08-06 15:34:07 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,670,384 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w17w08w19w110w113w218w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x24ca1902…7a87
0x34b655…2a6f
4 touches
1 conflict
0x2cee1585…4d13
0x34b655…2a6f
4 touches
1 conflict
0x4633fac1…c113
0x34b655…2a6f
4 touches
1 conflict
0x5dbb73e8…739f
0x34b655…2a6f
4 touches
1 conflict
0x8f3ce1f7…fafc
0x34b655…2a6f
4 touches
1 conflict
0x969a2e59…887c
0x34b655…2a6f
4 touches
1 conflict
0x98212952…9ba6
0x34b655…2a6f
4 touches
1 conflict
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 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity