← previous blocknext block →recent activity
Analyzing
Block #100,062,731
12 transactions · 12 stateful · 2026-08-29 02:16:09 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,062,731 · 12 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
1w02w03w17w08w19w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdabfe55d…df1c
0x40c49f…2af0
4 touches
1 conflict
0x6d5c5d72…914b
0x34b655…2a6f
4 touches
1 conflict
0xaa7d9546…81be
0x34b655…2a6f
4 touches
1 conflict
0xb75d08b2…3e12
0x34b655…2a6f
4 touches
1 conflict
0xc13cd6cc…281d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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: 0x40c49f17…d22af0
1 conflict on slot 0xdabfe55d45…a9df1c
Audit this contract →
← previous block·next block →recent activity