← previous blocknext block →recent activity
Analyzing
Block #98,453,275
20 transactions · 16 stateful · 2026-08-23 10:19:29 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,453,275 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w211w012w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86bd79a5…1f48
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x823c5bec…e738
0x99c7a7…8bf0
4 touches
1 conflict
0xe3ae148c…7cdd
0x99c7a7…8bf0
4 touches
1 conflict
0xc4c74438…20e5
0xc8689a…ee79
4 touches
1 conflict
0xd342f312…ff35
0x34b655…2a6f
4 touches
1 conflict
0x64b004ab…60af
0x754704…b603
4 touches
1 conflict
0x3129b531…9db1
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: Perpl
3 conflicts on slot 0x86bd79a5a6…961f48
Audit this contract →
← previous block·next block →recent activity