← previous blocknext block →recent activity
Analyzing
Block #100,603,893
28 transactions · 26 stateful · 2026-08-30 23:43:16 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.93
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,603,893 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w17w08w09w210w315w417w018w520w021w122w224w125w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xc9c17729…ac91
0x34b655…2a6f
8 touches
6 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
6 touches
3 conflicts
0x7db78f05…2895
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity