← previous blocknext block →recent activity
Analyzing
Block #98,092,394
31 transactions · 26 stateful · 2026-08-22 04:03:08 UTC
Parallelism
87/100
Blocked
46%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,092,394 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w08w09w112w113w215w016w117w219w221w324w025w128w130w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x736b9166…5ea5
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
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
6 conflicts on slot 0x736b916691…db5ea5
Audit this contract →
← previous block·next block →recent activity