← previous blocknext block →recent activity
Analyzing
Block #98,064,810
18 transactions · 12 stateful · 2026-08-22 01:44:19 UTC
Parallelism
89/100
Blocked
25%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,064,810 · 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
2w03w04w06w19w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x736b9166…5ea5
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0xe1026a65…aff5
0xd32edf…ff58
3 touches
1 conflict
0x00e84dca…18f9
0x34b655…2a6f
2 touches
0 conflicts
0x0f9f4d7a…326d
0x34b655…2a6f
2 touches
0 conflicts
0x186d62c5…e14a
0x34b655…2a6f
2 touches
0 conflicts
0x4b3b06fc…f6e2
0x34b655…2a6f
2 touches
0 conflicts
0x53a5e75a…e8ef
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 0x736b916691…db5ea5
Audit this contract →
← previous block·next block →recent activity