← previous blocknext block →recent activity
Analyzing
Block #97,514,348
14 transactions · 14 stateful · 2026-08-20 03:07:21 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,514,348 · 14 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
1w02w03w14w05w06w18w29w312w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x895ccfbd…8ab2
0x34b655…2a6f
8 touches
6 conflicts
0x3d354ff0…b7c5
0x34b655…2a6f
8 touches
6 conflicts
0x15ae3bf3…2507
0x34b655…2a6f
6 touches
3 conflicts
0xa3eee9fc…3e33
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x327c57dd…836d
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
6 conflicts on slot 0x895ccfbdec…418ab2
Audit this contract →
← previous block·next block →recent activity