← previous blocknext block →recent activity
Analyzing
Block #98,025,960
23 transactions · 16 stateful · 2026-08-21 22:28:50 UTC
Parallelism
91/100
Blocked
19%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,025,960 · 23 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
2w04w05w17w014w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0x825a1cb0…11fc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x65b1e075…7a54
0x34b655…2a6f
2 touches
0 conflicts
0x68dfc6ca…56ac
0x34b655…2a6f
2 touches
0 conflicts
0x6cd6078c…7e9b
0x34b655…2a6f
2 touches
0 conflicts
0x96d3e741…c328
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity