← previous blocknext block →recent activity
Analyzing
Block #93,486,898
17 transactions · 17 stateful · 2026-08-06 00:11:43 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,486,898 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w07w18w111w215w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb7e58c4…de8d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x91855e…ac7e
4 touches
1 conflict
0xff29965b…b918
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x37bef14c…a6d5
0x34b655…2a6f
4 touches
1 conflict
0x52b477bc…7ccf
0x34b655…2a6f
4 touches
1 conflict
0x5d832806…eb38
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xeb7e58c47e…69de8d
Audit this contract →
← previous block·next block →recent activity