← previous blocknext block →recent activity
Analyzing
Block #98,443,512
30 transactions · 27 stateful · 2026-08-23 09:30:21 UTC
Parallelism
93/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,443,512 · 30 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
5w07w08w115w117w018w123w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6b595a5d…894c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0x8e8d48a4…7a75
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
2 touches
0 conflicts
0x00000000…0002
0x63e48b…53f2
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0xf3d7a307cc…f14d63
Audit this contract →
← previous block·next block →recent activity