← previous blocknext block →recent activity
Analyzing
Block #102,204,612
18 transactions · 15 stateful · 2026-09-05 14:09:08 UTC
Parallelism
89/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,204,612 · 18 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
1w05w06w113w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x67d846dd…358c
0x284f45…7777
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0x49c1e49d…5192
0x9f3832…4ae4
4 touches
1 conflict
0x49c1e49d…5193
0x9f3832…4ae4
4 touches
1 conflict
0x7463d664…645c
0x9f3832…4ae4
4 touches
1 conflict
0x7cf5136f…ba69
0x9f3832…4ae4
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity