← previous blocknext block →recent activity
Analyzing
Block #94,967,460
18 transactions · 17 stateful · 2026-08-11 04:35:18 UTC
Parallelism
89/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,967,460 · 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
1w02w17w08w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c7c65d0…0b52
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xf5e30ed1…7017
0x065c9d…c394
3 touches
1 conflict
0x54526994…55b2
0x34b655…2a6f
2 touches
0 conflicts
0x7150753f…7e32
0x34b655…2a6f
2 touches
0 conflicts
0x87596feb…8947
0x34b655…2a6f
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: Perpl
1 conflict on slot 0x3c7c65d0e6…a00b52
Audit this contract →
← previous block·next block →recent activity