← previous blocknext block →recent activity
Analyzing
Block #84,141,076
13 transactions · 11 stateful · 2026-06-28 00:33:52 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,141,076 · 13 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
3w05w16w08w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc49465a6…c0c9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe3fc33e0…ccfb
0x34b655…2a6f
4 touches
1 conflict
0xb4cfbef1…2a21
0x40c49f…2af0
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x38ec2c24…ef42
0x34b655…2a6f
4 touches
1 conflict
0x3a3ae0e3…ac9b
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 0xc49465a60c…f1c0c9
Audit this contract →
← previous block·next block →recent activity