← previous blocknext block →recent activity
Analyzing
Block #102,204,281
12 transactions · 11 stateful · 2026-09-05 14:07:28 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,204,281 · 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
1w02w03w16w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b25d07f…1dee
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x962fe6c7…32c9
0x065c9d…c394
3 touches
1 conflict
0x173b64af…6c43
0x34b655…2a6f
2 touches
0 conflicts
0x2292bbf2…2551
0x34b655…2a6f
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 0x3b25d07f44…161dee
Audit this contract →
← previous block·next block →recent activity