← previous blocknext block →recent activity
Analyzing
Block #89,862,541
19 transactions · 16 stateful · 2026-07-24 07:54:27 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,862,541 · 19 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
10w013w016w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98f28768…1cde
0x34b655…2a6f
4 touches
1 conflict
0xa7d3e24a…0eb8
0x34b655…2a6f
4 touches
1 conflict
0xabdf81c9…b3b0
0x34b655…2a6f
4 touches
1 conflict
0xba8e1449…09a6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf18c12c4…3e7d
0x34b655…2a6f
4 touches
1 conflict
0x44b918e8…94d7
0x34b655…2a6f
4 touches
1 conflict
0x496ff651…1310
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 0x98f2876842…111cde
Audit this contract →
← previous block·next block →recent activity