← previous blocknext block →recent activity
Analyzing
Block #101,021,960
25 transactions · 23 stateful · 2026-09-01 10:46:45 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,021,960 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w09w112w014w115w216w317w120w121w222w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x297de2d5…7396
0x34b655…2a6f
4 touches
1 conflict
0x40f0cbff…df7c
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity