← previous blocknext block →recent activity
Analyzing
Block #98,743,919
31 transactions · 24 stateful · 2026-08-24 11:17:56 UTC
Parallelism
87/100
Blocked
46%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,743,919 · 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
1w02w03w04w15w29w311w012w015w116w219w121w323w127w328w230w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x36743f6f…476b
0x3bd359…433a
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0xa02838a3…bc54
0x34b655…2a6f
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity