← previous blocknext block →recent activity
Analyzing
Block #97,901,679
14 transactions · 14 stateful · 2026-08-21 11:58:08 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,901,679 · 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
1w02w03w16w27w38w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c20d376…0819
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xadb553c0…430a
0x34b655…2a6f
6 touches
3 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x75fe1fe5…d6f2
0x34b655…2a6f
4 touches
1 conflict
0x15907ea9…2fb5
0x34b655…2a6f
4 touches
1 conflict
0xa3fda367…40e1
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 0x4c20d37631…040819
Audit this contract →
← previous block·next block →recent activity