← previous blocknext block →recent activity
Analyzing
Block #91,446,562
14 transactions · 12 stateful · 2026-07-29 21:06:46 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,446,562 · 14 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
3w04w05w06w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d73f5bf…53ea
0x34b655…2a6f
4 touches
1 conflict
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0xda2ee2e7…968a
0x34b655…2a6f
4 touches
1 conflict
0x3cd98e7d…4628
0x34b655…2a6f
2 touches
0 conflicts
0x43d4717b…9a5e
0x34b655…2a6f
2 touches
0 conflicts
0x507e759e…81ec
0x34b655…2a6f
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 0x6d73f5bf40…ae53ea
Audit this contract →
← previous block·next block →recent activity