← previous blocknext block →recent activity
Analyzing
Block #98,677,693
18 transactions · 16 stateful · 2026-08-24 05:41:26 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,677,693 · 18 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
1w06w07w18w09w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x3f4d2f3d…d3b9
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa605468c…1bfc
0x2b46c0…1669
2 touches
0 conflicts
0x152a2f3e…13f8
0x34b655…2a6f
2 touches
0 conflicts
0x2431d060…6a71
0x34b655…2a6f
2 touches
0 conflicts
0x3f1e9b1d…ffd9
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 0x6ca15e14f4…917be8
Audit this contract →
← previous block·next block →recent activity