← previous blocknext block →recent activity
Analyzing
Block #93,363,457
18 transactions · 17 stateful · 2026-08-05 13:51:07 UTC
Parallelism
61/100
Blocked
47%
Avg conflicts / tx
0.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,363,457 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w17w28w312w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc467a38b…cf75
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0x8eef368f…aa21
0x34b655…2a6f
6 touches
3 conflicts
0x6659466a…5090
0x34b655…2a6f
4 touches
1 conflict
0x7fa44fe8…484e
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity