← previous blocknext block →recent activity
Analyzing
Block #84,324,176
14 transactions · 12 stateful · 2026-06-28 20:53:30 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,324,176 · 14 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
2w03w16w07w18w09w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb983f9fc…9b91
0xdde003…c9a4
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x23bcb6e8…566e
0x34b655…2a6f
4 touches
1 conflict
0x610aa855…5ecd
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0016
0x8fbe07…71b6
4 touches
1 conflict
0x0494780e…2900
0x8fbe07…71b6
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: 0xdde00377…29c9a4
1 conflict on slot 0xb983f9fc1c…ab9b91
Audit this contract →
← previous block·next block →recent activity