← previous blocknext block →recent activity
Analyzing
Block #100,919,238
16 transactions · 11 stateful · 2026-09-01 02:09:57 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,919,238 · 16 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
1w04w010w113w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x4ade28f6…ae28
0x34b655…2a6f
4 touches
1 conflict
0x2278b510…2725
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x87190df4…2e12
0x065c9d…c394
3 touches
1 conflict
0x87190df4…2e13
0x065c9d…c394
3 touches
1 conflict
0x28c56ea9…ca2c
0x065c9d…c394
3 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: 0x33176be2…ede078
1 conflict on slot 0x09106a952c…111467
Audit this contract →
← previous block·next block →recent activity