← previous blocknext block →recent activity
Analyzing
Block #98,012,825
18 transactions · 14 stateful · 2026-08-21 21:22:35 UTC
Parallelism
89/100
Blocked
43%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,012,825 · 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
2w03w04w17w08w19w110w011w112w013w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f8965bb…e238
0x34b655…2a6f
4 touches
1 conflict
0x1db5837f…1264
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x74a7b40b…8922
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc8f41960…e78e
0x34b655…2a6f
4 touches
1 conflict
0xce8fdb6c…227d
0x34b655…2a6f
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
1 conflict on slot 0x0f8965bbe3…2be238
Audit this contract →
← previous block·next block →recent activity