← previous blocknext block →recent activity
Analyzing
Block #98,459,943
17 transactions · 17 stateful · 2026-08-23 10:53:14 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,459,943 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w08w110w011w113w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xe3ae148c…7cdd
0x99c7a7…8bf0
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xecb0e4ba…7eb3
0x34b655…2a6f
4 touches
1 conflict
0x25d5e04e…3ef4
0x754704…b603
4 touches
1 conflict
0x64b004ab…60af
0x754704…b603
4 touches
1 conflict
0xba68e65e…c29a
0x754704…b603
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