← previous blocknext block →recent activity
Analyzing
Block #100,925,465
24 transactions · 22 stateful · 2026-09-01 02:41:17 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,925,465 · 24 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
1w04w05w18w09w110w213w014w115w016w118w219w323w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25180879…8191
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x24b08f9c…e594
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xb31206e6…a1e0
0x065c9d…c394
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc8cadee4…1bef
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 0x25180879df…1c8191
Audit this contract →
← previous block·next block →recent activity