← previous blocknext block →recent activity
Analyzing
Block #100,106,899
14 transactions · 14 stateful · 2026-08-29 05:58:31 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,106,899 · 14 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
1w02w15w09w010w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe759c8ad…6053
0x34b655…2a6f
4 touches
1 conflict
0xa1731f0f…1f9d
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca157308…ed43
0x34b655…2a6f
4 touches
1 conflict
0xd6e51c36…2064
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe759c8ad…6052
0x34b655…2a6f
4 touches
1 conflict
0x009a0451…b83e
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
1 conflict on slot 0xe759c8ad21…e96053
Audit this contract →
← previous block·next block →recent activity