← previous blocknext block →recent activity
Analyzing
Block #100,057,287
12 transactions · 12 stateful · 2026-08-29 01:48:45 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,057,287 · 12 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
1w04w05w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1867b653…e61b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x9912c5c1…f552
0x34b655…2a6f
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0xaf5c9d31…4547
0x065c9d…c394
2 touches
0 conflicts
0xd8393c19…4284
0x065c9d…c394
2 touches
0 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
2 touches
0 conflicts
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 0x1867b65332…1be61b
Audit this contract →
← previous block·next block →recent activity