← previous blocknext block →recent activity
Analyzing
Block #101,984,678
23 transactions · 21 stateful · 2026-09-04 19:34:10 UTC
Parallelism
87/100
Blocked
24%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,984,678 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w17w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x0c6a407c…2b73
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x04d4f30d…4dfb
0x34b655…2a6f
4 touches
1 conflict
0x29a58269…011a
0x34b655…2a6f
4 touches
1 conflict
0x2e957c13…4777
0x34b655…2a6f
4 touches
1 conflict
0x5746581b…0cb1
0x34b655…2a6f
4 touches
1 conflict
0x6823c28e…594c
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
3 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity