← previous blocknext block →recent activity
Analyzing
Block #98,287,271
14 transactions · 13 stateful · 2026-08-22 20:24:15 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,287,271 · 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
2w05w06w17w08w19w010w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x094cae63…148a
0x34b655…2a6f
2 touches
0 conflicts
0x15073066…40a5
0x34b655…2a6f
2 touches
0 conflicts
0x15e09cff…4280
0x34b655…2a6f
2 touches
0 conflicts
0x53ca1284…cb2c
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 0xf5dc501bf7…748313
Audit this contract →
← previous block·next block →recent activity